Hustle and Flow
summary
Argues that microservices should model processes not entities, showing concrete patterns and failures: paper-office simulation (catalogues, fax, mail cart) maps to queues and streams, rooting slip maps to command/event semantics, and the practical outbox pattern plus correlation IDs handle retries and eventual consistency. Demonstrates flow-based programming as an implementation model, cites Kafka/RabbitMQ/SNS‑SQS style brokers, and claims shifting to process-driven design avoids distributed monoliths and works in practice.
AI-written summary · about
chapters (15)
- 0:00Introduction to flow
- 1:43Sync vs async communication
- 4:52The problem with entities
- 7:07Modeling business processes
- 9:11Paper-based system analogy
- 12:50Commands and events
- 14:15Onboarding a restaurant
- 17:50Using routing slips
- 21:49Asynchronous order flow
- 25:09Hustle vs flow
- 28:25Handling errors and retries
- 31:49Event storming for process
- 34:28Flow-based programming
- 36:56Implementing flow-based
- 41:12Questions and answers
related talks
51mComplex Event Flows in Distributed Systems
20mDataflow Engines for Executing Cloud Applications: a Maslow's Hammer or Natural Outcome?
50mAddressing Recent Events
40mEverything Will Flow
47mThe Rise of Reactive Microservices
47mComplex event flows in distributed systems
47mAdopting Polyglot Flow
24mPatterns of Evolution from Monolith to Microservices