Using modern .NET technologies to decompose a monolith into micro-services
summary
Shows how to split a .NET monolith using Event Sourcing to record every change and projections to build read models (example: a customer event store and projector feeding Elasticsearch for search). Uses Kafka for messaging, OWIN/.NET hosts, and containerized services with blue‑green / gradual traffic shift via load balancer to roll versions. Covers concrete problems encountered: shared database pain, schema/versioning, testing networks, monitoring and rollback, and an incremental migration recipe rather than an all‑or‑nothing rewrite.
AI-written summary · about
chapters (14)
- 0:00Welcome and introduction
- 3:07Monolith challenges and pains
- 7:46Hype cycle of microservices
- 10:14Defining microservices
- 13:00Service isolation and boundaries
- 17:12Documentation and communication
- 20:22Domain-driven design
- 23:54Business logic and events
- 27:50Event sourcing and projections
- 31:18Team structure and ownership
- 35:10Deployment and rollback strategies
- 38:26Standards and compatibility
- 41:15Cloud and containerization
- 44:09Q&A and closing remarks
related talks
48mMicroMonolith
24mPatterns of Evolution from Monolith to Microservices
57mSplitting Monolith Application to Microservices
54mFrom a distributed monolith to a microservices solution
32mSplitting the monolith
36mMicroservices Lessons Learned
40mFrom Monolith to Observable Microservices using DDD
52mBuilding monolith applications that could scale to microservices..