|
|
|
|
|
by nullwasamistake
2589 days ago
|
|
TLDR the tooling is so bad it's basically impossible to run at scale. I worked for a company that tried. Maybe on a small scale it's fine, but replays and storage of past events takes insane amounts of space at high event rates. To the point that storage costs and replay times became a real problem. (Many terabytes and days) I also don't think it's a great idea in general. The event stream directly replicates a DB commit log, and the aggregates your tables. It's building your own database. We had to throw a year's worth of work away at the end so I'm fairly biased against trying it until the ecosystem is better. |
|