7 Strategies for Building Majestic Monoliths
summary
Seven concrete practices for building a refactorable monolith: bake in JaCoCo coverage via Maven to track tests, use GitHub Actions + Docker for build artifacts so the app can go to production at any time, design internal APIs-first and separate schemas per bounded context, prefer reactive paths or an in-memory event bus to avoid blocking, and demonstrate extracting a Barista as an Quarkus + Kafka extraction outpost that proves the Citadel can scale while keeping a 5-day deploy velocity.
AI-written summary · about
chapters (9)
- 0:00Introduction to Majestic Monoliths
- 3:37Code Quality and Test Coverage
- 6:26Continuous Delivery Practices
- 8:10Designing APIs in Monoliths
- 12:41Autonomous Data Strategies
- 14:46Avoiding Bottlenecks with Reactive Code
- 23:38Domain-Driven Design Basics
- 32:06Citadel and Outpost Pattern
- 39:18Q&A and Conclusion
related talks
47m7 Strategies for Building Majestic Monoliths
50mImplement the monolith - the one well modularized
59mMajestic Modular Monoliths
46mLove Your Monolith
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
52mMy Monolith Is Really Cool
01h 02mTools for simplified large scale systems