Querying Events
summary
A Complex Event Processing query language is implemented inside the Event Store and runs as JavaScript on V8 to let processors move to data instead of moving data to processors. It supports historical and continuous queries, linkTo reindexing for parallel folds, and emit/link semantics for composing results. The system is open source BSD and claims durability plus practical throughput: about 30,000 writes/sec and projections around 150,000 events/sec per node, so it works for large but not ultra low‑latency workloads.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:47Reactive Extensions
- 5:06Event Sourcing
- 6:43Temporal Correlations
- 9:35The Event Store
- 13:33Pattern Match
- 22:59Continuous Query
- 28:57Parallel Queries
- 29:41When Does an Event Change in a Mutable Model
- 38:29Event Sourcing
related talks
50mHow We Store 60,000 Events per Second
34mComplex Event Processing Made Easy with Cassandra and Quine Streaming Graph
47m8 years of EventSourcing/CQRS @ bettermarks: The good, the bad and the ugly
48mEvent Sourcing - what could possibly go wrong?
24mHow To Combine Event Sourcing Architecture In Your Node.js Server
51mThings I Wish I knew Before I Started with Event Sourcing
30mComplex Event Processing on Arbitrary Data in Real-Time
39mEvent Sourcing with Elixir