About this article
Thank you for visiting this site. This article is a guide listing all 8 articles in the “Software Architecture” category of the Architecture Crash Course for the Generative-AI Era series.
Software architecture is the layer that decides the structure, partitioning strategy, communication patterns, and technology selection of the entire codebase. Monolith or microservices, which language and framework to use, REST or GraphQL — the decisions that affect the entire development team.
Article index
1. Software Architecture Overview — Navigating a Domain Full of Camps
A bird’s-eye view of the three major patterns — monolith, modular monolith, and microservices — with recommended structures by scale. Software architecture is prone to “holy wars,” but this article provides practical selection criteria free from dogma.
2. Choosing a Programming Language — TS / Python / Java / Go / Rust
Compares TypeScript, Python, Java, C#, Go, Rust, Ruby, PHP, and C/C++ on four axes: scale, use case, talent market, and AI generation accuracy. Not “your favorite language” — a framework for choosing a language from project requirements.
3. Choosing an Overall Structure — Monolith / Microservices / Modular Monolith
How to decide your application’s overall structure. Beyond the three-pattern comparison, learn about the trap of premature decomposition into microservices at small scale and how to incrementally migrate from a monolith.
4. Module Design — Layered / Hexagonal / Clean
How to draw the “room partitions” inside an application. Compares Layered, Hexagonal, Onion, and Clean Architecture on three axes: domain complexity, team skill, and expected lifespan.
5. API Design Fundamentals — REST / GraphQL / gRPC / WebSocket
Explains when to use which of the four major styles: REST, GraphQL, gRPC, and WebSocket. Covers versioning strategy, authentication methods, and rate-limit thresholds — concrete, practical criteria for API design decisions.
6. Framework Selection — Spring / Next.js / FastAPI / Rails
Compares language-specific frameworks like Spring Boot, Next.js, FastAPI, and Rails. Evaluates LTS management, vulnerability response, AI generation accuracy, and five-year operability — selecting frameworks by sustainability, not hype.
7. Transaction Design — ACID / Eventual Consistency / Saga / Outbox
Covers ACID properties, isolation levels, distributed transactions, eventual consistency, Saga, Outbox, CAP theorem, and idempotency — the mechanisms that protect data integrity, complete with implementation patterns. Essential reading when adopting microservices or event-driven architectures.
8. Auth & Session Design — Server Sessions vs. JWT
Covers when to use server sessions vs. JWT, OAuth 2.0/OIDC flows, and safe Cookie attribute settings. Gives you the clear decision axis of “same domain → Cookie; cross-domain → JWT” from an implementation perspective.
Summary
This article listed all 8 articles in the Software Architecture category of the Architecture Crash Course for the Generative-AI Era series.
Software architecture is a domain prone to “holy wars,” but this series consistently provides selection criteria based on project scale, team, and requirements — free from ideological bias. Get the big picture from the overview, then dig into the themes that interest you.
For the overall series structure and other categories, see the master series index.
Hope you’ll check out the next article as well.