A huge part of serverless API design is handling retries or accidental resubmits. Without it, data integrity goes out the window.

Whenever we talk about serverless, there's always the one person who brings up cold starts.

I was recently honored with the title of AWS Serverless Hero. Here's my story.

Normalizing on standards for building microservices provides strong, consistent software anyone can pick up and maintain.

Learn what it took starting from nothing to getting two completely serverless apps live in production.

A multi-tenant application is a complex piece of software that could end in disaster if not built with these things in mind.

Serverless is gaining more and more popularity. What can we expect from it in the future

When designing an application you need to plan for three steps in the future. How can you design an app in a way that lets you iterate?

When talking about vendor lock-in, people rarely talk about data gravity. Do you need to consider it when going serverless?

Plus some bonus tips on how to get started