From a distributed monolith to a microservices solution

on YouTube ↗54m

" summary

A migration story that warns against a false microservices jump and shows concrete fixes: an integration service + thin B2B API, hit with thousands of requests per minute, becomes a distributed monolith when many tiny services share one SQL database and call each other synchronously. The salvaging tactics are specific: use Azure Event Grid for domain events, put storage queues between Event Grid and Functions, apply the outbox pattern, keep one domain responsible for its data and duplicate logic where practicality wins.

AI-written summary · about

" chapters (21)

1. 0:00Intro
2. 1:00Why a monolith
3. 2:30microservices vs monolith
4. 4:00no silver bullet
5. 5:15monolith to microservices
6. 6:15integration service
7. 8:00API management
8. 9:00Using our own API
9. 12:30A distributed monolith
10. 13:30The next service
11. 14:40The integration API
12. 15:45The business people
13. 19:30The solution
14. 22:55Functional domains
15. 23:55Implementation details
16. 25:15Do repeat yourself
17. 29:00loosely coupled code
18. 33:25event vs command
19. 38:48good practices
20. 46:35Bloat defense
21. 49:15Open close principle

" related talks

• 48mMicroMonolithMichal Franc · Codemotion Amsterdam 2017
• 36mDo Proper Monoliths before You Do Microservices!Jan de Vries · DevDays Europe 2019
• 43mMicroMonolith - Top anti-patterns of distributed systemsMichal Franc · NDC Oslo 2016
• 42mDo proper monoliths before you do microservices!Jan de Vries · Future Tech 2019
• 42mQ&A - Monolith to MicroservicesSam Newman, Sven Johann · GOTO Oslo 2020
• 36mMicroservices Lessons LearnedSusanne Kaiser · Voxxed Days Microservices 2018
• 31mMonolith to Microservices: A Guide to Seamless TransitionsDaniil Koshelev · Conf42 DevSecOps 2024
• 01h 03mFrom Monolith to Microservices: Story and PracticeKonstantin Gustov · DotNext 2018 Moscow