Comment on Turning the database inside-out (2015)parentComments−mkleczek1yI use the architecture you described as the go-to architecture for most of so called "business" applications (with PostgreSQL as dbms though).The missing pieces are:- incremental materialized view maintenance- (bi)temporal primary and foreign keys (upcoming in Pg18)Lately I found out about DBSP and Feldera which looks very promising as it is based on sound theory: https://github.com/feldera/feldera?tab=readme-ov-file#-theor...−dagss1yGreat link, thanks!What do you do postgres for consuming old events and smoothly transitioning to consuming new events? Anything like an event ID allocated at commit time that is usable? As I talk about in sibling comment..
Comments
I use the architecture you described as the go-to architecture for most of so called "business" applications (with PostgreSQL as dbms though).
The missing pieces are:
- incremental materialized view maintenance
- (bi)temporal primary and foreign keys (upcoming in Pg18)
Lately I found out about DBSP and Feldera which looks very promising as it is based on sound theory: https://github.com/feldera/feldera?tab=readme-ov-file#-theor...
Great link, thanks!
What do you do postgres for consuming old events and smoothly transitioning to consuming new events? Anything like an event ID allocated at commit time that is usable? As I talk about in sibling comment..