ZeBridge – PostgreSQL replicas on devices, synchronized over NATS

Re:ZeBridge – PostgreSQL replicas on devices, synchronized o... by ndrean on Tuesday November 10, 2026 @04:25AM (#50437914)

CRDT is useful when the application has a meaningful way to merge concurrent edits, if any. They don' replace database constraints or business rules. With LWW, you have a predictable winner when 2 devices replace the same value. Merging changes does not automatically preserve a unique realist: you need server validaation. LWW loses concurrent intents, but for many PG-backed applications, explicit/nderstandable conflict outcomes matters more than automatic edits preservation. BTW, what do you mean by dead comments?

[ Parent | on HN ]

Re:ZeBridge – PostgreSQL replicas on devices, synchronized o... by satvikpendem on Wednesday November 11, 2026 @07:39AM (#50452707)

Your comments don't actually show up, they're all flagged by default. I think you're shadowbanned, maybe email [email protected] to get it sorted out.

And yes I know all about business rules, but for my apps I need CRDTs which work as required for my business logic. LWW is not sufficient for me.

[ Parent | on HN ]

Re:ZeBridge – PostgreSQL replicas on devices, synchronized o... by ndrean on Wednesday November 11, 2026 @08:03AM (#50452915)

I understand. I needed rules, so LWW like Cassandra covered probably 80% of use cases. Otherwise, it is like Electric, all left to you.

[ Parent | on HN ]

Re:ZeBridge – PostgreSQL replicas on devices, synchronized o... by ndrean on Thursday November 12, 2026 @03:47PM (#50474035)

FYI, I added CDRT support (the same as PowerSync) and an example. It is agnostic, so you bring in your prefered library. It is not optimal though, I don't clean Postgres. I will push this.

[ Parent | on HN ]

Re:ZeBridge – PostgreSQL replicas on devices, synchronized o... by satvikpendem on Thursday November 12, 2026 @08:11PM (#50476815)

Thanks I'll look into it.

[ Parent | on HN ]