Building a serverless function or an API is easy. However, things get a bit more complicated as your application grows. What works for a few functions often doesn't work for hundreds of functions and services. As your application grows, you'll need to evolve your architecture, deployment, monitoring, and tooling.

This talk is a case study of the serverless startup's architecture evolution. We started with a single Lambda function in early 2018 and evolved our application through multiple stages and architectures. Currently, the application uses CQRS with GraphQL and more than 250 Lambda functions serving millions of requests.

We faced and solved many issues since we deployed our first Lambda function, learned a lot, and kept our infrastructure costs low (less than 1.5% of our MRR). And we do everything with a small team of fullstack developers without dedicated ops.

This was one of the previous versions of the same session: https://slobodan.me/talks/2024-06-13-serverless-days-milan/