Member-only story
7 AWS Serverless Design Principles for Solutions Architects
Discover how these principles translate to guidelines for architecting new projects
If you’ve worked with AWS in any sort of capacity, you’ve probably learned they have a unique way of doing things. They start off meetings reading documents in silence, they begin new projects by working backward, and no matter what they do, they drive their leadership principles… hard.
There’s a reason Amazon basically runs the world. Their way of doing things works.
Among the many artifacts they produce to help companies build best-in-class software are their general design principles. If you’ve ever been through an AWS Well-Architected review, you know all about them in excruciating detail (in a good way).
If you’re into building serverless applications, AWS has an entirely different set of design principles you should follow. They take the core pillars of the Well-Architected model and look at them through a serverless application lens.
Today, we’re going to take a look at all seven principles and talk about how those translate to your designs as a solutions architect.
1. Speedy, Simple, Singular
“Functions are concise, short, single…
