Is it safe to use Eventing and Node SDK with Sync Gateway on the same bucket?

Mobile Sync Gateway
1

I’m running Couchbase Server Enterprise 7.6.2 and Sync Gateway 3.1. I have Eventing functions and Node SDK upsert() operations writing to the same bucket that Sync Gateway monitors. This setup generally works, but occasionally, some documents end up with meta.xattrs = {} (empty object) instead of the expected _sync in xattrs, causing them to not sync to clients.

Is it safe to use Eventing and the Node SDK to update a bucket while Sync Gateway is listening to it? Or should I always use the Sync Gateway POST API for updates to ensure proper synchronization?

Thanks in advance for any insights.

2

As per Eventing — Server Compatibility | Couchbase Docs the minimum requirements are Sync Gateway 3.2 and Couchbase Server 7.6.3

1 Like
3

It’s generally safer to route writes through Sync Gateway’s API — direct bucket updates via Eventing or SDK can bypass the _sync xattrs logic, leading to exactly the issue you’re seeing.

1 Like