7 Strategies for Building Majestic Monoliths
summary
Seven concrete practices for building a monolith that’s easy to split later: use DDD with per‑bounded‑context packages and separate schemas, push public behavior through an API package, keep business logic inside aggregates and return immutable command/results, adopt reactive signatures with Mutiny/Uni to avoid blocking, leverage Quarkus’s Vert.x event bus for in‑memory async, and extract outposts by swapping one API implementation to Kafka. Live coding and full source live on GitHub (Quarkus Coffee Shop).
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:50The majestic monolith concept
- 5:59Coffee shop demo application
- 8:01Importance of code quality
- 10:06Continuous delivery practices
- 11:41Domain driven design
- 17:23API first design
- 19:41Autonomous data management
- 20:54Reactive programming
- 26:27Citadel and outposts
related talks
39m7 Strategies for Building Majestic Monoliths
01h 02mBuilding that glorious monolith. And carving it too.
02h 29mPractical advice for building glorious monoliths
52mBuilding monolith applications that could scale to microservices..
59mMajestic Modular Monoliths
45mHow I learned to stop worrying and love the monolith
50mMajestic Modular Monoliths
46mLove Your Monolith