You Keep Using That Word
summary
Argues that “asynchronous” is overloaded and unusable without context, contrasting request–response vs event‑driven semantics, showing request–response can be implemented both as blocking/non‑blocking (futures, reactive extensions) and via intermediaries, and that true temporal decoupling requires a broker with guaranteed delivery. Names brokers (RabbitMQ, Kafka, ActiveMQ) and cites Pat Helland and the Reactive Manifesto. Demonstrates pitfalls: awaiting makes non‑blocking code block, response routing should target any instance for resilience, and advises specifying exact properties needed.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:00Architecture and design
- 3:00Defining interaction styles
- 5:51The problem with async
- 9:40Industry definitions
- 12:31The reactive manifesto
- 16:31Non-blocking interactions
- 23:11Intermediaries and decoupling
- 30:04Implementation considerations
- 35:16The role of language
- 42:04Socio-technical communication
related talks
46mKeynote: You Keep Using That Word
44mFrom Synchronous to Asynchronous Distributed Microservices
01h 11mReactive Architecture Patterns Debate
02h 42m!!! Do not publish or share !!!!
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
54mReacting to an Event-Driven World
35mMaking Open Banking Responsive & Agile with Asynchronous and Event-Driven APIs
59mWays to Handle Non-blocking Returns in Message-passing Programs...