15 Real-world case studies

 

This chapter covers

  • How CodePen uses serverless for its preprocessors
  • How MindMup runs client APIs and file conversions

We’ve come to the end of this serverless journey. Through this book, you’ve learned what serverless is, how to use it in a new application, and how to migrate your existing applications to a serverless architecture. But we know that there is one important question you want to ask: Who is using serverless in production?

Hearing about companies using a new approach in production is always useful, along with the problems they’ve encountered and how it’s worked for them. In this case, another interesting question is why these companies felt serverless with Claudia.js was the right solution for them.

To answer that question, we chose two companies to ask about the challenges they’d faced, how and why they decided to go serverless, their architecture before and after going serverless, and the approximate costs.

Many companies are using serverless in production, and it was hard to pick the two best examples. But because you can read many success stories from enterprise companies using serverless on the AWS blog, we chose two companies that have successful products with small teams behind them. We think serverless allows you to move and scale quickly with a small team and a relatively low infrastructure cost, and we decided to show you how CodePen and MindMup are doing just that.

15.1 CodePen

15.1.1 Before serverless

15.1.2 Serverless migration

15.1.3 Cost of the infrastructure

15.1.4 Testing and challenges

15.2 MindMup

15.2.1 Before serverless

15.2.2 Serverless migration

15.2.3 Cost of the infrastructure

15.2.4 Testing, logs, and challenges

Summary