How the building blocks are arranged into whole-system architectures, and the patterns that make them resilient and evolvable. Part of the Architecture course.
- Monolith / Microservices / Serverless — [Intermediate] — the fundamental structural choice, and the honest tradeoffs (microservices are not a default)
- Resilience Patterns — [Advanced] — circuit breaker, bulkhead, retry, timeout, throttling — designing so partial failure stays partial
- Data & Integration Patterns — [Advanced] — CQRS, event sourcing, saga, materialized views, strangler fig
- Microservices Patterns — [Advanced] — service discovery, API gateway/aggregation, sidecar/ambassador, backends-for-frontends, leader election
- Transactional Outbox — [Intermediate→Advanced] — saving a change and announcing it without a dual write: lost vs phantom events, the outbox table and relay, at-least-once delivery, idempotent consumers. With a lab that crashes at the worst moments
Related
- Cloud Design Patterns (devops) — the same resilience patterns from the ops angle
- Orchestration (devops) — what microservices run on
- Distributed Systems — the theory these patterns manage
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering