The author, a former advocate for building 100% serverless cloud applications, now believes that the best way to build software is the one that solves the business problem with the lowest total cost of ownership.
They dispel myths around serverless services, such as they are only for serverless apps, prohibitively expensive "at scale," and that cold starts are always a problem. They also offer design considerations when introducing serverless into stateful apps, such as designing for elasticity, starting with orchestration, and designing for retry.
The author encourages solutions architects to explore the idea of integrating with a serverless service and to learn as they go.
















