Consuming Events Like There's No Tomorrow
summary
Explains how letgo processes very high event volumes (peaks over 10,000,000 events per hour, ~3,000/s) using domain events to decouple code. Describes the previous consumer architecture (including times when they ran ~100 machines) and the current approach, language-agnostic but with PHP tips and examples of using Akka from Scala or Java to build efficient consumers.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:06Domain events
- 10:37Synchronous integration problems
- 14:47Async event solution
- 25:16Domain event benefits
- 29:06Event consumption in Let's Go
- 33:59Event publishing in Let's Go
- 36:05Event router optimization
- 42:06Scala actor model
- 45:17Failure handling and backpressure
- 49:49Summary
- 51:13Q&A
related talks
54mReacting to an Event-Driven World
27mBUILDING A REAL-TIME AUCTION ENGINE USING EVENT SOURCING
29mEVENT SOURCING IN AKKA PERSISTENCE
50mDelicious Play recipes for real world
54mHow Events Are Reshaping Modern Systems
44mThe Art and Benefits of Computing Eventfully
53mDistributed Eventsourcing with Akka
27mFour Principles of Reactive Architectures