Event Driven Workflows
summary
A Go library lives at github.com/luno/workflow that turns sequential business processes into durable, distributed pipelines using event notification (no event sourcing), SQL-backed state with an outbox and support for reflex and Kafka as event streams. Workflows are directed acyclic graphs of from→to steps with timeouts, callbacks and branching; testing helpers fake time for fast acceptance tests. It is pre-1.0, reaches production after months of iteration, already runs KYC report processing on the critical path and trades lower latency for stronger durability.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 2:37Event-driven architecture
- 5:52Design philosophy
- 12:00Execution mechanics
- 16:26Implementing the workflow
- 25:53Q&A and closing remarks
related talks
27mWorkflow library in Go for API development
28mAn introduction to the Workflow Development Kit
39mEvents, Workflows, Sagas? Keep Your Event-driven Architecture Sane.
45mDapr Workflows: How to Write Reliable, Fault-Tolerant Applications...
53mActors and Workflows: Different, Yet the Same
51mComplex Event Flows in Distributed Systems
16mExoFlow: A Universal Workflow System for Exactly-Once DAGs
01h 38mBuilding Reliable Distributed Systems