couchbase-eventing

To handle document mutations in Couchbase Eventing, write JavaScript OnUpdate and OnDelete handlers that process source keyspace changes. You must configure source and metadata keyspaces, then use bindings to route derived documents to target collections.

Couchbase Eventing timer callbacks fail when handler logic is not idempotent or when the metadata keyspace is missing. Ensure safe use of bindings and verify that the metadata keyspace is properly configured to track timer execution state.

Using N1QL queries inside a Couchbase Eventing function requires configuring SQL++ bindings in your deployment settings. This allows your JavaScript handlers to execute N1QL queries against the cluster while processing document mutations.

External HTTP calls are supported in Couchbase Eventing functions using curl. You must enable curl in your deployment configuration and ensure your handler logic safely manages timeouts and external API responses without blocking workers.

Troubleshoot Couchbase Eventing backlog and performance issues by tuning worker counts and diagnosing failed invocations. Check deployment state, verify DCP stream health, and optimize handler logic to reduce processing bottlenecks.

The best way to deploy Couchbase Eventing functions safely is using from_now deployments for zero-downtime updates. Configure workers, bindings, and consistency settings carefully, and ensure handler logic is idempotent before deployment.