Hustle and Flow
summary
Argues that Flow‑Based Programming (from J Paul Morrison, 1970s) maps real paper workflows into inbox/outbox services so event-driven systems stay asynchronous, with data in information packets and behavior in components. Shows a “Just Paper Takeaway” example using faxes, a Franz Kafka mail broker, queues-as-storage and retries, and models error handling via separate error ports. Recommends practical tools: value stream mapping, event storming and projections to design reliable async flows that reduce temporal coupling.
AI-written summary · about
chapters (18)
- 0:00Start
- 5:07Where Can We Learn about How We Succeed with Asynchronous Workflows
- 6:15Value Stream Map
- 6:44Lead Time
- 9:47Fax Machines
- 14:41Reference Data
- 17:25The Order Wheel
- 23:10Errors in Asynchronous Systems
- 25:44Declined Transactions
- 27:28Advice Which Is More Practical for Software Engineers
- 28:01Dominant Paradigm
- 29:18Flow-Based Programming
- 34:33Flow Based Programming
- 41:21Errors Flow
- 44:16Value Stream Mapping
- 45:42Handovers
- 48:05Event Storming
- 52:55Event Modelling
related talks
50mHow Flow Works & Other Curiosities
50mHow Flow Works
24mKeeping the flow going: Data-flow oriented workflow systems
51mComplex Event Flows in Distributed Systems
01h 09mExploring Flow Architectures
53mGetting into the Flow: building applications with Reactive Streams
38mDistributed Workflows with Flowy
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging