Eventing Service

The Eventing Service provides near real-time handling of changes to data; whereby code is executed either in response to mutations, or as scheduled by timers.

About the Eventing Service

The Eventing Service is a framework to operate on changes to data in a cluster. These changes to data are known as events, and the Eventing Service allows Functions to be written, saved, and triggered in real time in response to events. Events include changes made to specified items, and the arrival of scheduled points-in-time.

Functions offer a computing paradigm that developers can use to handle data changes. In the cluster, you can use Functions to handle data-changes according to an event-condition-action model. This can include generating threshold-based alerts, as well as propagating data changes and moving documents to a different bucket inside a cluster. Functions also provide an easy option to perform cascade deletes.

For more detailed information about Eventing Service, refer to Eventing Service: Fundamentals.

Using the Eventing Service

Like the other Couchbase services, the Eventing Service can be deployed during cluster creation, or by adding it to an existing cluster. The Eventing Service depends on the the Data Service. This service must also be deployed on the cluster in order to use the Eventing Service. (Information about how these services interact with one another can be found in the Couchbase Server documentation.)

If a cluster has the Eventing Service deployed, Eventing Functions can be created and managed using the Couchbase SDK, the REST API, and the Couchbase Cloud UI.