Do proper monoliths before you do microservices!

on YouTube ↗06m

" summary

Claim: build a proper monolith first and only move to microservices when you truly need global scale. Most real projects have 2 to 8 development teams and are forms-over-data systems that work fine with an Angular or MVC frontend, a .NET backend, an ORM and a single database. Monoliths here last decades; early microservices add latency, coupling and brittleness (a Jenga tower) and often fail within months unless designed around clear capabilities like checkout and update profile.

AI-written summary · about

" chapters (6)

1. 0:00Intro
2. 0:54Microservices
3. 2:28Microsoft
4. 3:22Monoliths
5. 4:00Disadvantages
6. 4:50How to start

" related talks

• 36mDo Proper Monoliths before You Do Microservices!Jan de Vries · DevDays Europe 2019
• 42mDo proper monoliths before you do microservices!Jan de Vries · Future Tech 2019
• 42mQ&A - Monolith to MicroservicesSam Newman, Sven Johann · GOTO Oslo 2020
• 37mEvolutionary Architecture & MicroservicesRebecca Parsons · GOTO Chicago 2015
• 47mMicroservices? Monoliths? An Annoying Discussion!Eberhard Wolff · JCON-ONLINE 2021
• 43mMicroMonolith - Top anti-patterns of distributed systemsMichal Franc · NDC Oslo 2016
• 53mDon’t Build a Distributed Monolith: How to Avoid Doing Microservices WrongJonathan "J." Tower · NDC Porto 2023
• 14mMonolith 2 MicroServices Houston we've got a problemMike Francois · Voxxed Days Microservices 2018