Breaking Up The Monolith With EQ

on YouTube ↗27m

" summary

Argues that emotional‑intelligence markers predict when a team can safely split a monolith and offers concrete signals: regular package publishing and daily deploys, a maintained integration test suite (not blind 100% coverage), documented API ownership, and hands‑on event modeling. Recommends tools and practices like event storming, outside‑in thinking for API design, stop sharing DB connections and migrate to GraphQL/REST/Protobuf interfaces, and prefer small reproducible services in familiar languages rather than chasing novelty.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 3:48Emotional Intelligence?
3. 9:17Why Not A Rewrite?
4. 10:37How Do Microservices Intersect Emotional Intelligence
5. 10:59Conway's law
6. 16:35Freedom of Languages

" related talks

• 45mHow I learned to stop worrying and love the monolithNikola Zivkov · JDD 2018
• 46mLove Your MonolithMike Lehan, Cal Evans · Dutch PHP Conference 2022
• 36mDo Proper Monoliths before You Do Microservices!Jan de Vries · DevDays Europe 2019
• 47mBreak Up the Monolith: Testing MicroservicesMarcus R Merrell · Selenium Camp 2019
• 47m7 Strategies for Building Majestic MonolithsJeremy Davis · JCON WORLD ONLINE 2023
• 43mBreak Up the Monolith: Testing MicroservicesMarcus R Merrell · Selenium Conference India 2018
• 39mConsidering Migrating a Monolith to Microservices?Chris Richardson · YOW! Melbourne 2022
• 27mBreak up Monoliths and lay them to REST!Arun Narayanaswamy · Apidays LIVE Paris 2020