Software Architecture by Example
summary
Uses an architecture kata to design an online auction that must scale from hundreds to thousands of participants, concluding the domain forces a distributed solution with two distinct bid-capture paths (one ultra-reliable for auctioneers, one highly elastic for online bidders). Builds components—auction session, bid capture, bid tracker, payment, video stream—maps them to a microservices topology and resolves ordering with event queues (FIFO durable queues) rather than distributed transactions. Mentions Excalidraw sketches and O’Reilly videos as teaching artifacts.
AI-written summary · about
chapters (10)
- 0:00Introduction to kata
- 1:58Auction system requirements
- 4:10Defining characteristics
- 11:37Analyzing requirements
- 17:14Distinguishing domain needs
- 21:24Logical component design
- 29:22Iterative design process
- 34:26Choosing architectural styles
- 43:39Mixing styles and patterns
- 52:24Resources and conclusion
related talks
45mSoftware Architecture by Example
57mSoftware Architecture: The Hard Parts
50mA Practical Use Case of Software Architecture Evolution
03h 08mSoftware Architecture for Developers (3-hour workshop)
01h 03mAgile Software Architecture
01h 00mDescribing and Documenting Your Architecture
43mThe hitchhiker's guide to software architecture and design
49mBuilding Scalable Applications at Mercado Livre with SOLID & Clean Architecture