How To Combine Event Sourcing Architecture In Your Node.js Server
summary
Claims that event sourcing in Node.js scales to millions of users and simplifies migrations and recovery by keeping an immutable event log and materialized views. Shows a lightweight Twitter demo and a Node.js server with a Node.js + Mongoose event schema, materialized view builders running as 10s batch consumers, and a transaction engine used for banking. Recommends storage and tooling like Event Store, Hadoop (web HDFS), Couchbase, events-tour and nest CQRS and event-streaming with Apache Kafka / kafka-node for high throughput.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:54Building Newsfeed
- 15:51Advantages
- 18:44NPM Libraries
- 19:18Batch Consumer
- 20:09What Is Happening In The Real World ?
- 21:33Stream Processing
related talks
28mEvent Sourcing a Node.js Application
48mEvent Sourcing - what could possibly go wrong?
52mEvent Sourcing for the Cloud Developer
48mNodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?
39mEvent Sourcing made Simple
44mEvent-driven Revolutions: From Monolith to Event Sourcing in Practice
44mEvent Sourcing - You are doing it wrong
40mEvent Sourcing: the good, the bad and the complicated