Software Architecture
The styles, principles, and trade-offs behind how real systems are structured, from a single monolith to distributed microservices.
software-architecturesystem-designengineeringintermediate
Get Yaaddi on Google Play Free. Install the app, then add this course from its Course Library.
View this course's repo on GitHub → — star it, open an issue, or suggest a fix.
41decks
41main cards
144practice cards
0%with images
v1.1.5version
Card type mix
- multiple choice: 121
- true false: 44
- select blank: 41
- match pairs: 11
- multi select: 6
- order: 5
What's covered
- What Software Architecture Actually Is
- Architecture vs Design vs Code
- Quality Attributes (the "-ilities")
- Architectural Decision Records
- Identifying Architecture Stakeholders
- Monolithic Architecture
- Layered (N-Tier) Architecture
- Microservices Architecture
- Event-Driven Architecture
- Service-Oriented Architecture
- Serverless Architecture
- Modular Monolith
- Hexagonal (Ports & Adapters) Architecture
- Clean Architecture
- Pipe-and-Filter Architecture
- Separation of Concerns
- Coupling and Cohesion
- SOLID Principles Overview
- Domain-Driven Design Basics
- Bounded Contexts
- CQRS
- Event Sourcing
- Synchronous vs Asynchronous Communication
- REST API Design Basics
- Message Queues and Brokers
- API Gateways
- Service Discovery
- Database per Service vs Shared Database
- Consistency Models: Strong vs Eventual
- Caching Strategies
- The CAP Theorem
- Horizontal vs Vertical Scaling
- Load Balancing Basics
- The Circuit Breaker Pattern
- Retry and Backoff Strategies
- Rate Limiting
- Observability: Logs, Metrics, Traces
- Security in Architecture
- Documenting Architecture (the C4 Model)
- Making Architecture Trade-offs
- Recap: Key Terms
Example cards
multiple choice
What makes a decision architectural?
multiple choice
Which is the broadest zoom level?
Latest: Haiku review fixes: corrected factual errors and cards that did not match what their lesson teaches.