Three Microservice Patterns to Tear Down Your Monoliths
summary
Claims a practical path to break a monolith by storing only events in one MySQL table as a persistent queue, using Spring Boot writers that return an immediate receipt and sequence number, and tiny reader services that event sourcing replay and materialize state into in-memory caches polled every second. Uses Eureka for discovery, WebSockets for client event feeds, Speedment to generate DB mappings, and supports snapshotting for large histories. Demo booking app runs, scales per-service, is eventually consistent, and the code is on GitHub. CQRS materialized views
AI-written summary · about
chapters (10)
- 0:00Start
- 4:13Definitions
- 5:32Example App: Booking System
- 22:07First Pattern: Event Sourcing
- 23:58Second Pattern: Materialized Views
- 31:55Booking App Implementation
- 33:00How to Scale Up/Down
- 37:47Implementation: Object-Relational Mapping
- 38:57Implementation Booking Service
- 42:19Implementation Calendar Service
related talks
52mBuilding monolith applications that could scale to microservices..
24mPatterns of Evolution from Monolith to Microservices
45mBuilding Monoliths that Could Scale (Easily) to Microservices (If They Need)
46m" Slicing Monolith into a CQRS / Event sourcing microservice: joys and pains"
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
47mEvent-Driven Microservices = Microservices Done Right
46mMicroservices Data Patterns: CQRS & Event Sourcing
51mPatterns & Practices of Implementing Event-driven MicroSvc...