Recap: Architectural Styles

Five styles by what each makes easy, and the rule for choosing.

Styles differ by what ships together and how the parts talk (Five Ways to Divide an Application).
A monolith is one deployable; the modular monolith keeps its parts apart inside (Monolithic Architecture: One Deployable Unit).
Layers organise code inside a deployable; they are not a way to deploy it (Layered Architecture: Presentation, Business and Data).
Microservices deploy separately and own their data, and pay in network calls and operations (Microservices: Small Services, Each With Its Own Database).
Event-driven services announce what happened and others react, at a cost in visibility (Event-Driven Architecture: Services That React to Events).
Serverless functions run on demand, with cold starts and per-call pricing (Serverless Architecture: Functions Run on Demand).
Start with the simplest style the team can run, and divide for a named pressure (Choosing a Style for a Team and a Product).
A shared database joins services that deploy apart (Microservices That Share One Database).

← → move through sections and cards