Hacker News Reader

Couchbase is a very very different product under the hood. Be aware you have to run Couchbase with their minimum spec cluster requirements ( 3 nodes, tons of CPU and RAM ) just to ensure you don't lose data because it syncs from ram to disk at best every 100ms

View on HN

Hod @ Couchbase here. This is inaccurate. Couchbase does not delay in writing to disk (some other dbs do). You typically want 3 nodes for high availability and failover, but it isn't required. Auto replication can also help avoid loss in many failure scenarios.

I'd actually love to be proven wrong, Couchbase looks awesome on paper but some Couchbase staff even confirmed this with me here https://forums.couchbase.com/t/persistence-durability-guaren...

This is complicated, because you're intertwining Sync Gateway and Couchbase Server.

Couchbase Server queues writes immediately. The default is to ack once a write is in Server memory, but you can choose other options. See the response from daschl in that thread.

I see what you were trying to get at with your question. I'm not sure we clarified enough what's going on. I'll respond on the forum.

Reply on news.ycombinator.com