7 ms·
PostgreSQL. The WAL is an event log, and when you squint at its internal architecture, you’ll see plenty of overlap with distributed event sourcing.
by jgraettinger1 2y ago
PostgreSQL.
The WAL is an event log, and when you squint at its internal architecture, you’ll see plenty of overlap with distributed event sourcing.
- marcosdumay 2y agoAlmost every modern software system. Anything running over the Web is event driven.
- lolive 2y ago99.99% of the data we consume on the Web comes out of databases [call it Transactional-SQL-xxx or ColumnBased-yyy or Elastic-SaaS-zzz].
- marcosdumay 2y agoWell, yes. Databases are event driven themselves. As is any web application, because the web (at least without sockets) is constrained into communicating events only. Also, most local GUI applications, because people just like events better for it.
- mrkeen 2y agoLikewise with git. There's the "top-level events" that you see (commits). But even when you're doing 'unsafe' operations, you're working with the lower-level reflog events.
- lmm 2y agoRight. The hard part is already done. Which makes it infuriating that it's all "internal". Every serious RDBMS already contains an implementation of an event-sourcing system, but you're not allowed to actually use it.