You Keep Using That Word: Asynchronous And Interprocess Comms (Remote)
summary
Argues that "asynchronous" is ambiguous and unusable, replacing it with concrete choices: request–response vs event-driven interactions, client-side non-blocking clients for parallel calls (example: award-points 50ms + upgrade-sub 150ms sums to 200ms but runs in ~150ms when parallelized), or broker-backed communication for temporal decoupling with guaranteed delivery, retries and idempotency. Calls out VM SLA realities (no per‑VM uptime guarantee) and recommends specifying exact failure and latency behaviors instead of waving the word asynchronous.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:48Term asynchronous confusing
- 3:57Request-response vs event-driven
- 7:51Problems with asynchronous
- 10:22Definitions of async comms
- 13:09Reactive Manifesto’s async
- 15:59Non-blocking client limits
- 24:02Temporal decoupling
- 29:45Service failures handling
- 35:49Context for technical terms
- 40:11Oxford Dictionary async
- 43:03Socio-technical systems
- 46:31Beyond sync and async
- 48:56Q&A
related talks
53mYou Keep Using That Word: Asynchronous And Interprocess Comms
52mYou Keep Using That Word: Asynchronous And Interprocess Comms
01h 01mYou Keep Using That Word: Asynchronous And Interprocess Comms
38mYou Keep Using That Word
42mYou Keep Using That Word
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
44mFrom Synchronous to Asynchronous Distributed Microservices
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
