Do proper monoliths before you do microservices!

on YouTube ↗42m

" summary

Argues that designing a well-structured monolith first avoids the pain of a distributed monolith built on a shared SQL Server and brittle HTTP chains; describes a real pipeline of web job → parsing API → processing API → public business API that became slow and cascadingly fragile, and a cloud stack using Azure Functions, Service Bus, App Service, IdentityServer and SQL Server. Notes teams are often <100, and cites an org with ~400 services where ~300 duplicated name/address data, fixed pragmatically with one person DB and 300 service-specific views and no brittle correlation ID plumbing.

AI-written summary · about

" chapters (10)

1. 0:00Introduction and setup
2. 1:28Monoliths vs microservices debate
3. 5:07Designing silos in monoliths
4. 8:44Problems with distributed monoliths
5. 13:51Case study of flawed microservices
6. 22:01Proper monolith design approach
7. 29:30Scaling from monolith to microservices
8. 34:04Design vs implementation complexity
9. 38:45Pragmatism in architecture
10. 41:20Closing and contact

" related talks

• 36mDo Proper Monoliths before You Do Microservices!Jan de Vries · DevDays Europe 2019
• 06mDo proper monoliths before you do microservices!Jan de Vries · Build Stuff 2019
• 54mFrom a distributed monolith to a microservices solutionJan de Vries · NDC Sydney 2020
• 53mDon’t Build a Distributed Monolith: How to Avoid Doing Microservices WrongJonathan "J." Tower · NDC Porto 2023
• 48mMicroMonolithMichal Franc · Codemotion Amsterdam 2017
• 43mMicroMonolith - Top anti-patterns of distributed systemsMichal Franc · NDC Oslo 2016
• 42mQ&A - Monolith to MicroservicesSam Newman, Sven Johann · GOTO Oslo 2020
• 43mHow to Avoid Doing Microservices Completely WrongJonathan "J." Tower · Update Conference Krakow 2025