Design more decoupled services with one weird trick
summary
Claim: generate the ID up front at step minus one and each vertical slice stores its own data keyed to that ID, so events carry only identifiers instead of fat payloads. Uses event-driven pub/sub, vertical slice architecture, micro frontends and GUIDs (client or server) and transactional-session techniques. Example: a 25‑field checkout becomes slim events like order accepted event carries only the ID, snapshots prices for bookings, avoids shared databases and measurably reduces logical coupling and broker load.
AI-written summary · about
chapters (13)
- 0:00Decoupling services intro
- 1:10Coupling in software history
- 5:04Microservices rise and challenges
- 8:56Technology vs logical coupling
- 12:52Solution to decoupling services
- 15:03Event-driven architecture basics
- 21:24When event-driven works best
- 27:51Vertical slice architecture
- 37:41Data coupling in workflows
- 42:16One weird trick
- 51:09Trick in real-world use
- 55:21Search across services
- 57:28Summary
related talks
58mFinding your service boundaries - a practical guide
39mBuilding next-gen applications with event-driven architecture
54mThe Dark Side Of Events
58mDesigning for change with Vertical Slice Architecture
26mMicroservice Architecture Based on Event Sourcing
51mScaling yout Architecture with Services and Events
49mReactive microsystems
50mDeveloping Microservices with Aggregates