Architecture patterns
The framing to internalise before any of the content: patterns are vocabulary, not virtue. You get points for naming the pattern a design already implies, for using a shared name to speed up a conversation, and for knowing when a pattern is overkill. You lose points for pattern-driven design. Interviewers at this level are often testing for restraint, not for the catalog.
This chapter also carries the org-design vocabulary, because at staff and lead level architecture and org structure are the same conversation. Conway's law runs both directions, and the inverse Conway maneuver is the tool.
What this chapter covers
- [done] Team Topologies and splitting a team
- [done] The repository pattern, and the argument against
- [done] CQRS: the adoption ladder
- [done] Resilience patterns
- [done] Load shedding, backpressure and degradation
- [done] The five fixes for CQRS eventual consistency
- [done] Vertical slices, and the anti-pattern catalog
- [done] Event storming, worked on a real domain
- [done] The GoF subset that actually appears
- [done] Sidecar, ambassador and adapter
- [done] The standards reference card
- [done] DDD strategic design
- [done] DDD tactical design
- [done] Event sourcing, sagas, and the transactional outbox
- [done] SOLID, hexagonal, refactoring vocabulary, decision machinery
- [done] Modular monolith vs microservices
Source: §29, §31, §35, §42.