Monolith? Microservices? Who cares?
summary
Argues that architecture choice matters far less than code modularity and deployment setup: moving between monolith and microservices is trivial if code follows simple rules, otherwise it fails. Cites using Java 11 modules, static checks like ArchUnit/Structure101 and a proper CI/CD pipeline to enforce boundaries. Notes you can only truly validate architecture in production, warns deployment constraints often drive architecture decisions, and invokes the 80/20 Pareto tradeoff for ROI on tests and refactors.
AI-written summary · about
chapters (4)
related talks
47mModular Monoliths
01mModularization: Foundation of Microservices and Monoliths
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
46mLove Your Monolith
49mRealizing Domain Design Through Architectural Modularity ...
01h 04mModular Monoliths and Other Facepalms
36mIt's Simple...
01h 01mModular Monolith Instead of Microservices: How, When and Why
