Building monolith applications that could scale to microservices..
summary
Argues that start-with-a-monolith plus DDD, CQRS and event sourcing lets a system evolve into microservices only when needed, not as a premature goal. Shows a concrete conference Q&A example with command models, event models, projections and aggregates, implemented with Axon Framework on Spring Boot, using an event store and message broker (Ascot server) and GitHub samples. Demonstrates state rebuilt from events, location transparency, and working code to extract modules later.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:30Agenda
- 4:03Microservices Architecture
- 8:25Burst Approach
- 11:21Example
- 14:32CQRS
- 18:43Domain Driven Design
- 25:00Examples
- 26:06Projections
- 30:08Modularity
- 30:49Events
- 32:51Event Sourcing
- 34:54Why Event Sourcing
- 37:04Location Transparency
- 39:53Independent Models
- 40:49Event Stores
- 49:16Summary
related talks
45mBuilding Monoliths that Could Scale (Easily) to Microservices (If They Need)
39mPragmatic Microservices with DDD, CQRS and Event Sourcing Using Axon Framework
02h 29mPractical advice for building glorious monoliths
47mThree Microservice Patterns to Tear Down Your Monoliths
24mPatterns of Evolution from Monolith to Microservices
20mMonolith to Microservice: Story of a Transformation...
36mDo Proper Monoliths before You Do Microservices!
46mAxon Framework : A CQRS Approach to Microservices