Shifting Gears: From Events to Event-Driven
summary
Company shifts from fire-and-forget events to a true event-driven platform using DynamoDB streams, EventBridge and an outbox pattern with Lambda, SQS and fan‑out consumers. Legacy RabbitMQ had ~45,000 undelivered/dead‑letter items; new approach lets an isolated instant‑match product launch in weeks, keeps services decoupled, and runs paper‑use compute. Results: faster feature iteration, bounded contexts identified via event‑storming, £1.2bn payments processed in a year, GMV £22.7bn (2023) and a sale every three minutes.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:47Agenda
- 2:58Where we started
- 8:06Events without purpose
- 12:22Becoming event-driven
- 20:42It's all about the teams
- 33:00Bring the business along
- 37:55Arriving at the destination
- 42:43What's next?
- 44:13Takeaways
- 45:19Outro
related talks
43mEvent-Driven Evolution with AI as my Partner in Design
54mSo You Want to Build An Event Driven System?
44mThinking Asynchronously: App Integration Patterns for Microservices
56mDesigning Event-Driven Applications to Improve Scalability
24mModernise using Event-Driven Architectures
25mData-Driven Migration from Monoliths to Event-Driven Microservices
29mStreaming & Eventing for Top Management
29mAPIs and Event Streaming Dualty