Keynote: You Keep Using That Word
summary
Claim: “asynchronous” is too vague for engineering decisions. Definitions collapse into three concrete concerns: non-blocking (futures and async/await), temporal decoupling via broker, and routing/state assumptions that force either stateless processing or complex state replication (two major outages cited from replication). Examples: request/response over queues, event-driven vs RPC, Netflix/reactive extensions, Temporal for durable orchestration. Recommended action: specify which of those behaviors is required rather than saying “make it asynchronous.”
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:45Defining communication terms
- 3:46The ambiguity of asynchronous
- 7:43Reactive manifesto and definitions
- 11:52Non-blocking and future patterns
- 18:26Intermediaries and decoupling
- 23:59Stateful vs stateless processing
- 30:50Orchestration and reliability
- 33:35The importance of shared language
- 39:24Conclusion and takeaways
related talks
47mYou Keep Using That Word
02h 42m!!! Do not publish or share !!!!
17mKeynote: Is it Reactive or Eventful? Aren't they the Same?
49mNeed for ASYNC: in pursuit of scalable internet-scale applications
38mChoreography vs Orchestration in long running asynchronous processes
46mKeynote III: Mind Your State for Your State of Mind
44mFrom Synchronous to Asynchronous Distributed Microservices
52mLoosely or lousily coupled? Understanding communication patterns