I’ll never use an Oracle product and IBM is a soulless corporation. Debian is a much better product anyway but they’re missing some of the really good enterprise features that Red Hat has. I hope at some point they have solutions for Satellite and IDM.

There’s a reason Meta can’t operate Threads in Europe. They don’t abide by the GDPR.

Buckets are like databases in traditional relational databases. Here’s the doc on how to filter which documents get replicated.

https://docs.couchdb.org/en/stable/replication/intro.html#controlling-which-documents-to-replicate

Normally with XDCR you can specify which documents to replicate out of a bucket. It doesn’t have to be the entire bucket. So if you had certain types (comments, upvotes, etc) then only those would sync when the target comes online.

I did check into Apache CouchDB, the open source upstream, and replication is there. We use Enterprise Couchbase at work and it’s a dream but there are some tools that I use that only use Apache CouchDB (Inkdrop for example). It’s worth looking into.

Actually XDCR is not available in the community edition so that option is gone. Sorry about that.

Sorry. I didn’t realize XDCR was not available in the community edition.

It is a NoSQL database but the SQL syntax is ANSI SQL compliant. If you moved the queues to Couchbase and let it handle the replication and consistency, you wouldn’t have to code for it.

Using Couchbase as your eventual consistency database is perfect for this scenario. It’s designed for this type of thing. Even if systems are offline for a few days they will queue up and replicate when they come back online. Cruise ships use it for this very reason.