Events in Our Applications: Event Bus and Distributed Systems
summary
Describes an event bus architecture where PHP services publish JSON events to RabbitMQ, consumers run as individual Docker containers, logs go to an ELK stack, and tests use an in-memory adapter that mimics the bus. Events are immutable objects with three fields (name, payload, timestamp); the system uses requeue/ack strategies for transient vs permanent failures, supports schema migration, and coordinates long-running processes via saga patterns (orchestration vs choreography).
AI-written summary · about
chapters (14)
- 0:00Event-driven intro
- 2:27Commands and events in CQRS
- 4:36Immutable objects and messages
- 7:04Sync vs async events
- 8:51Microservice integration issues
- 10:37Event Bus for distributed systems
- 13:33RabbitMQ in event systems
- 16:02Event handling abstractions
- 19:57Practical event sending
- 23:13Error handling in events
- 25:41Saga pattern for long processes
- 30:21Choreography vs orchestration
- 32:33Testing event architecture
- 35:32Q&A
related talks
51mComplex Event Flows in Distributed Systems
26mEvent Driven APIs
01h 08mEvent Driven Architecture – Enabling Microservices
57mSimplify Your Architecture: Events and Publishing
50mMoving from legacy to event-driven with Kafka
28mHow APIs and Event driven architecture [...]
46mState or events? Which shall I keep?
43mEvent Streams & Data Rapids: Harnessing the Full Power of Messaging Platforms.