Just-in-time Architecture

on YouTube ↗55m

" summary

A games team moves from a monolith to microservices, discovers an accidental distributed monolith with availability coupling (three 99% services yield ~97% system availability — about 11 days/year downtime), then adopts an event-driven design using TypeScript code, event sourcing and a transactional outbox to guarantee events, and an orchestration-style process manager to issue commands, handle retries and compensating transactions while accepting eventual consistency and added observability.

AI-written summary · about

" chapters (9)

1. 0:00Just-in-time Architecture intro
2. 1:29Games company’s journey
3. 8:05Monolith to microservices pitfalls
4. 14:24Why distributed monoliths fail
5. 15:26Event-driven architectures
6. 22:50Event-driven communication
7. 31:12Scaling architecture evolution
8. 33:38Checkout workflow live code
9. 35:31Q&A

" related talks

• 49mJust in Time ArchitectureMacklin Hartley · NDC Porto 2023
• 55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable DevelopmentChris Richardson · iSAQB Software Architecture Gathering – Digital 2021
• 01h 03mMicroservices vs The Distributed MonolithChris Riley · PHP UK Conference 2024
• 40mCAPtivating architecture: Navigating Distributed Systems and MicroservicesAlexandros Charos · Voxxed Days Thessaloniki 2024
• 48mIT Architecture : All your micro-services are wrong PERIOD!Dwight Matthys · Voxxed Days Brussels 2023
• 27mThe technical journey to microservicesRuss Miles · The Lead Developer London 2015
• 59mHow to Escape The Distributed MonolithIan Cooper · NDC Minnesota 2019
• 01h 08mEvent Driven Architecture – Enabling MicroservicesBrad Irby · Silicon Valley Code Camp 2018