Behold The Monolith: Understanding Microkernel Architecture
summary
Argues that monoliths remain viable by using the microkernel (plug‑in) architecture, shows a recycling app example where thousands of device‑specific assessment rules live as plugins (JAR/DLL or simple Java packages) and a registry implemented as a map points to them; contracts use an interface with assess/register/deregister methods; mentions tooling like OSGi, Prism, Jigsaw and serverless lambdas for remote plugins; warns that core system is a single deployment and single point of failure, and that plugin‑to‑plugin dependencies are an anti‑pattern.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 1:12What is microkernel architecture
- 8:41Microkernel in business apps
- 10:27Plugins and contracts
- 24:54Microkernel vs microservices
- 34:36Microkernel vs hexagonal
- 37:49Disadvantages and anti-patterns
- 42:25When to use microkernel
- 44:53When not to use microkernel
- 48:24Q&A and closing
