Those API Calls Could Have Been a JOIN!!
summary
The talk explains risks of premature microservice distribution—fragmented domain models and many API calls that could have been a database JOIN—and advocates applying Event-Driven patterns inside a modular monolith. It presents Spring Modulith Events as a way to implement event-driven design while keeping a single deployable app, and shows using AsyncAPI for event documentation when you later decide to scale to distributed services.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 5:24Event-driven architecture
- 11:03Point-to-point integration problems
- 12:31Domain events solution
- 14:44Synchronous vs asynchronous events
- 16:28Spring Modulith transactions
- 19:56Event Publication Registry
- 23:47Externalizing events
- 26:16AsyncAPI event specs
- 31:57Demo: monolith architecture
- 39:07Publishing external events with AsyncAPI
- 42:16Q&A
related talks
32mUnifying API and event driven architectures
01h 03mMicroservices vs The Distributed Monolith
43mHow to Avoid Doing Microservices Completely Wrong
36mDo Proper Monoliths before You Do Microservices!
55mIs it Time to Abandon Microservices? Modular Monoliths Rescue Your Wallet!
52mBuilding monolith applications that could scale to microservices..
26mMetamorphosis: Microservices & Event-driven Architecture
24mPatterns of Evolution from Monolith to Microservices