Understanding Microservices: a guide for the monolithic developer
summary
Shows a concrete path from monolith to microservices using a modular monolith that snaps into independent services, demonstrated with an ASP.NET 6 Tacky Tacos sample. Uses Dockerized RabbitMQ (a RabbitMQ topic exchange) and SignalR so an order API publishes messages the kitchen service consumes, visible in the RabbitMQ UI. Introduces Steeltoe + Eureka service discovery with two instances on ports 50005/50006 alternating jokes. Emphasizes incremental Kit Kat pattern, database per service, and “don’t roll your own” auth.
AI-written summary · about
chapters (21)
- 0:00Microservices intro for monolith devs
- 1:53Ready for microservices?
- 2:57Microservices ecosystem
- 4:05Monolith to microservices transition
- 8:17Decomposing monolith into modules
- 10:24Modular monolith approach
- 12:34Defining service scope
- 15:46Avoiding over-scoping services
- 18:15Sync vs async communication
- 22:54Event-driven architecture
- 24:19Live demo: async messaging
- 32:40Database per service rule
- 36:17Eventual consistency challenges
- 37:23Data-first vs code-first
- 38:48Security in distributed systems
- 41:19API Gateway as entry point
- 43:28Service discovery and registry
- 46:03Demo: Netflix Eureka discovery
- 51:49Key microservices considerations
- 53:12Deployment and monitoring
- 54:37Resources and next steps
related talks
01h 14mUnderstanding Microservices: A Guide For the Monolithic Developer
43mGo micro with Microservices
24mPatterns of Evolution from Monolith to Microservices
52mMicroservices: A Utopian Mystery
50mEmbracing Microservices
49mMicroservices: An unexpected Journey
37mKnee Deep in Microservices
57mEmbracing Microservices