Designing Infrastructure-Free Systems
summary
Starts from a monolith and shows concrete refactors: delete duplicate address code, add an airlock namespace to isolate third‑party interfaces, split components using facades + queues and RabbitMQ exchanges, then apply the Blackjack refactoring to split services with zero downtime. Moves deployments from VMs to serverless, solves cold starts (avoid cron hacks), enforces statelessness, idempotency via unique event IDs, petitions for fast deletes, and mentions a platform called Marake that handles messaging and availability.
AI-written summary · about
chapters (18)
- 0:00Infrastructure-free systems
- 1:25Monolith origins
- 3:52Fixing deployment errors
- 5:17Spaceship architecture model
- 8:50Event-driven design
- 12:22Blackjack pattern refactoring
- 15:52Monolith to microservices
- 16:35Evaluating serverless versus virtual machines
- 18:41Cold starts impact
- 21:12Chaos in distributed systems
- 22:16Killing services in prod
- 24:44Idempotency for chaos
- 26:31Immutable data
- 27:53Solving congestion
- 28:37Code quality tools
- 33:13Formal verification
- 33:55Key takeaways
- 35:18Q&A
related talks
57mBuilding Systems that are #neverdone
54mServices, Services, Everywhere!
46mLove Your Monolith
43mMicroMonolith - Top anti-patterns of distributed systems
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
24mPatterns of Evolution from Monolith to Microservices
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
01h 03mMicroservices vs The Distributed Monolith