Architecture Decisions and Migration Paths Cheat Sheet
|
This content was generated with the assistance of AI and should be verified against the official documentation before being relied on in production; see the section bibliography for the reference material consulted while preparing these pages. |
A single-page, colour-coded summary of the whole Architecture Decisions and Migration Paths section, built around "where are you now? — what to do": migration paths grouped by current starting point, a monolith-vs-microservices signal box, a benefits/inconveniences comparison, the layering box, a new-project recommended-stack matrix, a pitfalls strip, and pointers to the primary online sources — handy for quick memorization or as a printable desk reference.
For the full explanation, every worked example, and every figure, see the dedicated pages:
Foundations — Architectural styles: monolith, modular monolith, microservices, Benefits and drawbacks of microservices, and Choosing: monolith or microservices?.
Layering the architecture — Layering: isolating backend and frontend and API gateway and backends for frontends.
Migration paths — Migration overview: how to approach any migration, Migration path: from a legacy stack to a modern one, Migration path: from a monolith to a modular monolith, Migration path: from a monolith to microservices, and Migration path: from single-tenant to multi-tenant SaaS.
Starting from scratch — Starting a new project: which path and which technologies.