The technical journey to microservices

on YouTube ↗27m

" summary

Adoption hits an adoption hump where money and effort produce little value; successful journeys use concrete patterns: keep all domain happenings in event lakes, apply event sourcing with projections to build aggregates and views, accept eventual consistency, and test contracts by mandate tests on different platforms. Chaos practices like Simian Armies introduce stress to drive antifragility. Expect extra integration tests, blue/green deploys and bespoke tooling; monoliths often win when stability is the priority.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 5:22Microservices adoption failures
3. 7:32Defining microservices
4. 10:26Aligning microservices with business
5. 15:23DDD and events in microservices
6. 20:02Designing for change
7. 22:35When microservices fail
8. 24:03Antifragility and ethics

" related talks

• 24mPatterns of Evolution from Monolith to MicroservicesKarina Mora · HashiTalks 2022
• 45mMicroservices: A retrospectiveTomer Gabel · Øredev 2019
• 52mMicroservices: A Utopian MysteryPraveena Fernandes · GOTO Copenhagen 2016
• 57mEmbracing MicroservicesGrzegorz Piwowarek · GeeCON Prague 2023
• 45mBuilding and evolving microservices: lessons from the frontlinesIlias Bartolini · Codemotion Rome 2018
• 39mConsidering Migrating a Monolith to Microservices?Chris Richardson · YOW! Melbourne 2022
• 01h 03mThe Magic of Small Things - 10 Years of MicroservicesJames Lewis · GOTO Copenhagen 2024
• 49mMicroservices: An unexpected JourneySam Newman · JavaDay Ukraine 2017