Technology stack - Locize is serverless
No servers?
We believe the best DevOps is NoOps.
Nothing against DevOps (or DevOps people) — quite the opposite. We just think we can do things differently.
Instead of spending time setting up and maintaining virtual machines, we build on managed services — leaving us more time to work on product features.
Building Locize gave us the opportunity to explore a more “serverless” path for long-lasting components.
At a high level, we use these AWS building blocks:
And in particular:
AWS Lambda
AWS Lambda is a compute service where you upload code and AWS runs it for you. No servers to manage, no containers to operate, no infrastructure to babysit.
For Locize, Lambda integrates especially well with:
- Amazon S3 — where we serve localized files
- Amazon DynamoDB — our main storage for work-in-progress data
That means we don’t have to worry (as much) about capacity planning, scaling, or multi-server coordination.
We use the Node.js runtime for our Lambda functions.
Amazon API Gateway
AWS API Gateway lets you create a RESTful API to expose selected back-end features. The back end can be another AWS service, such as AWS Lambda or AWS DynamoDB, or it can be an existing web application.
How Locize uses these services
What about the client side?
In another blog post.