I Made Everything Loosely Coupled. Does My App Fall Apart?
summary
Argues that loose coupling is a trade-off not an ideal, showing a serverless loan‑broker built with SNS/SQS, EventBridge, Step Functions and CDK where composition is code and the automation CDK composes boxes and lines actually defines runtime coupling. Explains how publish/subscribe, topic hierarchies and field filters work (EventBridge topic hierarchies), warns of data duplication, eventual consistency and infinite loops from event storms, and recommends choosing coupling based on control, ownership and deployment automation.
AI-written summary · about
chapters (8)
- 0:00Intro
- 3:04Thinking like an architect
- 8:55Of boxes & lines
- 14:06Drawing a line
- 20:16Connections & coupling
- 27:55Messages & Events
- 40:38Composition, cloud-style
- 47:29Outro
related talks
52mLoosely or lousily coupled? Understanding communication patterns
42mLoosely or lousily coupled?
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
51mHiding The Lead: Coupling, Cohesion, and Microservices-Style
46mHiding The Lead
53mHiding The Lead
44mHiding The Lead
01h 03mMicroservices vs The Distributed Monolith