You Keep Using That Word
summary
Explains why the word “asynchronous” is useless without context and gives precise distinctions: non-blocking vs blocking (futures, await and parallel calls), temporal decoupling via a message broker intermediary (queues, responses not necessarily returning to the same instance), tradeoffs around latency, idempotency and state, and practical patterns for making systems robust. Expect concrete examples, rationale for when brokers help, and actionable phrasing to use instead of the vague word asynchronous.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05Arrows in service architectures
- 3:33Term asynchronous communication
- 7:23Definitions in distributed systems
- 10:53Non-blocking versus synchronous
- 12:21Benefits of non-blocking calls
- 19:27Temporal decoupling and intermediaries
- 27:53Ambiguity of asynchronous
- 33:13Socio-technical systems
- 35:17Defining communication terms
- 37:03Question and answer session
related talks
01h 01mYou Keep Using That Word: Asynchronous And Interprocess Comms
52mYou Keep Using That Word: Asynchronous And Interprocess Comms
38mYou Keep Using That Word
53mYou Keep Using That Word: Asynchronous And Interprocess Comms
49mYou Keep Using That Word: Asynchronous And Interprocess Comms (Remote)
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
26mAsync API for Event Driven Architecture
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging