Loosely or lousily coupled?
summary
Argues that commands vs events decide dependency direction while synchronous versus asynchronous decides temporal coupling, not the other way round; shows a working Java Spring Boot example on GitHub using Kafka/RabbitMQ/REST and orchestration (Camunda, BPMN) for long‑running processes with state and scheduling to track SLAs; warns event-driven systems can turn into a “pinball” architecture and recommends a pragmatic mix of choreography and orchestration so order fulfillment, payments and onboarding stay visible and controllable.
AI-written summary · about
chapters (4)
- 0:00Start
- 10:49Example: Build a pizza ordering app using events
- 17:16Example: Build a pizza ordering app via orchestration
- 38:33Types of Coupling
related talks
52mLoosely or lousily coupled? Understanding communication patterns
48mI Made Everything Loosely Coupled. Does My App Fall Apart?
47mComplex event flows in distributed systems
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
51mComplex Event Flows in Distributed Systems
32mBalancing Choreography & Orchestration
01h 13mOrchestration vs. Choreography in Microservices
38mChoreography vs Orchestration in long running asynchronous processes