Find your bearing in software architecture
Find your bearing in software architecture.
A vendor-neutral field guide to every major kind of architecture: what each one is, where it fits, where it fails, and how to choose between them.
Founded and edited by Abhinav Taduka, an enterprise software architect working across payments, public-sector systems and cloud modernization. Read his writing.
Eight bearings to start from
- 000°Software architecture stylesMonoliths, microservices, event-driven, hexagonal and the rest: how a system is shaped.
- 045°Cloud architectureWell-architected design, landing zones, multi-cloud and cost as an architectural concern.
- 090°Data architectureWarehouses, lakes, lakehouses, data mesh and streaming pipelines.
- 135°Integration architectureAPIs, messaging, ESBs, API-led connectivity and event streaming between systems.
- 180°Security architectureZero trust, identity, secrets, threat modeling and secure-by-design systems.
- 225°AI & ML architectureRAG, agents, model gateways, MLOps and governance for AI in production.
- 270°Enterprise architectureTOGAF, capability maps, governance and aligning technology with the business.
- 315°Platform & infrastructureKubernetes, platform engineering, infrastructure as code and service meshes.
Also on the chart
- Solution architecture Turning requirements into a design: quality attributes, decision records, stakeholders.
- Frontend & mobile architecture Rendering strategies, micro-frontends, backends-for-frontends and offline-first apps.
- Industry architectures Reference designs for payments, healthcare, government and other regulated domains.
Tools for the journey
- Comparisons Two architectures side by side, with a verdict on when each wins.
- Glossary Plain-English definitions for the terms architects use.
- Certifications What each exam covers, who it suits and how to prepare.
- Best practices Cross-cutting patterns: resilience, idempotency, observability.