Event Processing in Action
summary
Hands-on guide to building event-driven systems using CI examples like Jenkins, Travis, Tim City and a working pattern of producers → channel → consumers with an intermediate event processor vs consumer role that enriches but does not decide. Key rules: events are immutable and named in past tense, include scenario/reference/state data, handle absent/uncertain events, extract duplicated logic into separate consumers, and rely on small components with component tests for easy change and extension.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:00What is clean code
- 11:24Events
- 14:08Interactions
- 16:11Complex Events
- 24:57Data Information
- 29:04Event Processor
- 32:36Consumer
- 39:51Producer
- 42:58Producer Consumer
- 47:08Summary
related talks
51mEvent Processing in Action
54mHow Events Are Reshaping Modern Systems
51mComplex Event Flows in Distributed Systems
38mEvent Design & Event-first Development
46mManaging Event Driven Architectures
03mEvents on the Outside, on the Inside, and at the Core
47mComplex event flows in distributed systems
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets