Understanding Microservices: A Guide For the Monolithic Developer
summary
Guides a monolithic team through an incremental path from a modular monolith to microservices using a real Tacky Tacos demo built on ASP.NET 6, Docker and YARP, showing runnable examples with RabbitMQ pub/sub and Eureka via Steeltoe. Recommends starting with large modules (the Kit Kat pattern), insists on DB per service for deployability, contrasts synchronous front-end APIs with asynchronous back-end events, and shows the demos working end to end while warning about eventual consistency, telemetry and added operational complexity.
AI-written summary · about
chapters (14)
- 0:00Microservices for monolithic devs
- 1:18Need microservices?
- 8:49Decomposing a monolith
- 16:45Satellite pattern for scaling
- 20:28Service scope and boundaries
- 27:27Sync vs async communication
- 31:47Database per service
- 37:54Security and API gateway
- 46:10Service discovery demos
- 51:06Q&A on consistency
- 57:08Convincing your boss
- 1:01:46Breaking off satellites
- 1:05:17Cross-cutting concerns
- 1:12:03Final advice for monoliths
related talks
57mUnderstanding Microservices: a guide for the monolithic developer
50mEmbracing Microservices
57mEmbracing Microservices
43mGo micro with Microservices
24mPatterns of Evolution from Monolith to Microservices
52mMicroservices: A Utopian Mystery
37mKnee Deep in Microservices
52mI Have a Microservices Architecture and I Didn't Know.
