About this article
Thank you for visiting this site. This article is the master index for the entire Architecture Crash Course for the Generative-AI Era series.
The series comprises over 80 articles organized into 11 categories. Each category index page lists every article it contains, along with a brief summary of “what it covers” and “what you’ll learn.”
Use this article as a map, and jump into whichever category is most relevant to you.
How to navigate the series
The following articles introduce the series as a whole and help you pick a reading order that fits your role.
If you’d like to understand the role of an IT architect first, start here.
If you get stuck on a term, use the glossary as a reference.
Category index
1. System Architecture (12 articles)
The layer that decides the infrastructure skeleton — hardware, OS, networking, and cloud. Covers 12 decision axes for system foundations: how to choose a cloud vendor (AWS/Azure/GCP), runtime environments (VM/container/serverless), network design, BCP/DR, and cost management.
Recommended for: Infrastructure engineers, cloud architects, anyone adopting cloud for the first time
2. Software Architecture (8 articles)
The layer that decides the structure, partitioning strategy, communication patterns, and technology selection of the entire codebase. Covers monolith vs. microservices, language selection, API design (REST/GraphQL/gRPC), and transaction design — the decisions that shape the skeleton of your code.
Recommended for: Backend engineers, tech leads, anyone involved in architecture selection
3. Application Architecture (5 articles)
The layer that defines the rules inside the code. Covers SOLID principles, DDD, naming conventions, and error handling — the rules every member of the development team follows in daily coding. It may look unglamorous, but it has the most direct impact on long-term development velocity.
Recommended for: All programmers, especially those establishing team conventions
4. Frontend Architecture (9 articles)
The only layer the user touches. Covers rendering strategies (CSR/SSR/SSG/ISR), state management, framework selection (React/Vue/Svelte/Astro), CSS design, BFF, browser security, and SEO — a comprehensive tour of frontend design decisions.
Recommended for: Frontend engineers, full-stack engineers, anyone involved in UI/UX
5. Data Architecture (7 articles)
The layer that designs how data is stored, flows, and is governed. Covers datastore selection, modeling, DWH/data lake/lakehouse, ETL/ELT, streaming, and data governance. In the AI era, data is the fuel for AI, and this category’s importance grows every year.
Recommended for: Data engineers, ML engineers, anyone driving AI adoption
6. Security Architecture (8 articles)
Security cannot be bolted on after the fact. This category covers how to embed security into the design from the start — authentication, authorization, encryption, network security, zero trust, secrets management, and vulnerability scanning.
Recommended for: Security engineers, all architects (security is everyone’s responsibility)
7. DevOps Architecture / DevOps / SRE (15 articles)
The largest category in the series, designing the entire flow of build, ship, and run. Covers version control, CI/CD, testing, deploy strategies, monitoring, log design, SLO, incident response, SRE practices, documentation, and ticket management — the full dev-ops lifecycle.
Recommended for: DevOps engineers, SREs, platform engineers, dev team leads
8. Enterprise Architecture (6 articles)
The domain of designing an entire organization’s IT strategy as a unified whole. Covers the BA/DA/AA/TA four-layer model, TOGAF, and ArchiMate — the knowledge needed to prevent the “local optimum, global catastrophe” where each department builds near-identical systems independently.
Recommended for: CIOs, CDOs, corporate strategy/IT strategy divisions, enterprise architects
9. Solution Architecture (5 articles)
The domain of design focused on solving a specific project’s problem. Covers requirements definition, quantifying non-functional requirements, ROI calculation, and PoC design — the craft of translating technology decisions into business cases and winning with numbers. If EA is the city plan, this is the blueprint for an individual building.
Recommended for: Solution architects, project managers, anyone involved in proposals and estimates
10. Case Studies (7 articles)
The category where theory meets specific scales, industries, and phases in practice. Six cases — solo/startup, mid-sized SaaS, large enterprise, public sector, mobile-first, and AI product — demonstrate how the right answer changes completely for the same design question depending on context.
Recommended for: Anyone who wants to sharpen their judgment through a case close to their own situation
11. Appendix (3 articles)
Cross-cutting reference material for the entire series. Three articles — an anti-pattern catalog (what not to do), a best-practice catalog (the safe defaults when in doubt), and a major-incident case study collection (lessons from the industry’s most expensive mistakes) — that double as design review checklists.
Recommended for: Pre-review preparation, post-series reflection
Suggested reading paths
You don’t need to read everything in order. Pick a path that matches your role.
Backend engineer: System Architecture → Software Architecture → Application Architecture → DevOps Architecture
Frontend engineer: Frontend Architecture → Application Architecture → DevOps Architecture → Security Architecture
Manager / PM: Solution Architecture → Enterprise Architecture → Case Studies → System Architecture Overview
New grad / early career: Series introduction (arch-intro-overview) → What is an IT Architect → Application Architecture → Software Architecture
For more detailed role-based reading orders, see the Learning Roadmap article.
Summary
This article presented a bird’s-eye view of all 11 categories and 80+ articles in the Architecture Crash Course for the Generative-AI Era series.
Architecture knowledge is the bundle of knowledge whose value appreciates the most in an era where the value of writing code is declining. You don’t need to learn everything at once. Start with the category closest to your daily work and build outward from there.
Hope you’ll check out the next article as well.