Comment by kiitos
2 years ago
A CRDT is a discrete entity/object that has to follow a set of rules for reads, writes, and storage -- including, but not limited to, rules about how to maintain history. You can certainly mix-and-match CRDTs with other entities in the same database, but you can't like "fold in" arbitrary changes to a CRDT without following the rules.
> you can't like "fold in" arbitrary changes to a CRDT without following the rules.
Thanks. I was thinking a few simple rules, like last outside change wins, or monitoring changes and recording the time. But that wasn't realistic.
A separate service still seems like a big win, but I'll have to assume there are similar reasons for it being tightly tied to Postgres.