Instead, they’re using a micro-services, API-driven, serverless architecture approach. They use three AWS products: AWS API Gateway (which manages incoming API calls and converts them into other AWS jobs); AWS Lambda (the event-driven computing platform that executes actions when required); and DynamoDB (AWS’s NoSQL database as a service).
Lambda, one of AWS’s newer services, is the key enabler. Developers upload their code to Lambda and the system carries out functions. Think of it like the popular app “If This Then That” (ITTT). In both systems, an event triggers actions. For example, ITTT can automatically save a photo taken on your phone to DropBox. Or ITTT can automatically save any update to Twitter in a Google Drive document.
Lambda and ITTT are not related, but they work similarly. Lambda can automatically convert an image uploaded into AWS’s Simple Storage Service (S3) and resize it. Lambda can automatically take information uploaded to a database and place it in an analytics tool for further analysis.
At its most basic level, Panse and Nagtegaal have programmed Lambda so that when a Teletext.io customer takes an action an API call is made to AWS. The API Gateway triggers a Lambda function to run and Lambda integrates with DynamoDB to retrieve stored data needed to execute the user’s request.
This serverless architecture has advantages, the company says:
Functions are only executed when needed, so there are no virtual machines or servers to fail. “Lambda functions … only appear when needed. And what isn't up, can't come down.”
And you only pay for functions that are executed. Teletext.io’s costs correlate directly to how many customers are using the service. When no customers use the service, Teletext.io isn’t paying for Lambda functions to be executed or API calls to be made. The only idle cost is the storage of data in DynamoDB.
Sign up for CIO Asia eNewsletters.