You Keep Using That Word: Asynchronous And Interprocess Comms
summary
Claim: the word "asynchronous" is meaningless without context because people use it to mean different things — non-blocking/await code using futures or reactive extensions (parallel HTTP/gRPC calls to loyalty and subscription reduces end-to-end latency), message broker inbox patterns (queues, RabbitMQ, Kafka, response queues) that give temporal decoupling and durability, or event-driven vs request/response semantics (10,000-stock event, 5,000 threshold). Brokers solve availability but add routing and state complexity; stateless services work better.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:03Microservices communication styles
- 4:16Synchronous vs asynchronous
- 8:51Request-response vs event-driven
- 10:35Meaning of asynchronous
- 13:43Definitions from Twitter and Reactive Manifesto
- 17:11Non-blocking calls and limits
- 23:49Non-blocking ≠ asynchronous
- 26:58Temporal decoupling and brokers
- 31:52Durability of intermediaries
- 37:30Ambiguity of asynchronous
- 41:19Shared meaning matters
- 45:11Beyond vague terms
- 48:17Q&A
related talks
42mYou Keep Using That Word
53mYou Keep Using That Word: Asynchronous And Interprocess Comms
52mYou Keep Using That Word: Asynchronous And Interprocess Comms
49mYou Keep Using That Word: Asynchronous And Interprocess Comms (Remote)
38mYou Keep Using That Word
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
59mSucceeding at Reactive Architecture