Modular Monoliths and Other Facepalms
summary
Argues that modular monolith is rebranding rather than a new style, tracing modularity back to the 1960s and showing the same principles reappear; documents that teams moved to microservices to enforce partitioning but microservices often reinforce poor partitioning and reports surprising scales (some “micro” services reach ~1,000,000 LOC, estimates of ~20M developers and many starting since the pandemic); cites concrete systems like Mars Curiosity: C99 on VxWorks with heavy static analysis to show modularity, interfaces and fault protection actually work.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:33Modular monoliths facepalm
- 3:02Monoliths vs microservices cycle
- 10:02Future is unevenly distributed
- 11:27What monolith means
- 13:58Meaning of micro in microservices
- 20:36Defining microservices
- 23:08Object orientation and modularity
- 27:18History of modularity
- 31:58Why modular monoliths make sense
- 35:51Modularity beyond services
- 40:08Three modularity layers
- 43:00Challenge of naming
- 46:30Trade-offs in architecture
- 54:29Boundaries and modular programming
- 57:19Conway's law and teams
- 1:02:34Software fashion industry
related talks
51mModularization: Foundation of Microservices and Monoliths
01h 01mModular Monolith Instead of Microservices: How, When and Why
43mModular Monoliths: The Architecture That Scales w Your Domain
56mModular Monolith and the Prisoner of Microdisservices
59mMajestic Modular Monoliths
50mMajestic Modular Monoliths
57mModularizing the Monolith
43mMonolith? Microservices? Who cares?