API Components

The Reactive Streams standard, available at (http://www.reactive-streams.org) describes various API components. These are all implemented for the Oracle NoSQL Database Streams API. Briefly, these are the major API components:

API Description More Informatin

API	Description	More Informatin
`NoSQLPublisher`	Aggregates table operations into a single stream, and publishes them according to the configuration received from its subscriber(s). For any Java JVM, create only one `NoSQLPublisher` class instance for a publisher configuration. You can create multiple publishers per JVM, as long as their configurations differ. For example, you can create a single JVM to support two or more publishers, each connecting to different stores with their different configurations. You can scale the streaming service to use multiple subscribers to stream events from Oracle NoSQL Database store.	`NoSQLPublisher` is introduced in the chapter titled Using a Streams Publisher. For more information about scaling the streaming service to use multiple substribers, see Scaling a Streams Application. For more information on `NoSQLPublisher`, see NoSQLPublisher.
`NoSQLSubscriber`	Interface that you must implement to define how to process each store operation, warning, and error. `NoSQLPublisher` manages each `NoSQLSubscriber` instance that you provide. The `NoSQLPublisher` can use multiple `NoSQLSubscriber` instances.	For an introduction to subscriber implementation, see Implementing Subscribers. For information about how to use multiple subscribers streaming events from Oracle NoSQL Database store, see Scaling a Streams Application. For more information on `NoSQLSubscriber`, see NoSQLSubscriber.
`NoSQLSubscription`	Represents a single subscription that you created. This class receives `write` and `delete` events present in the operations stream, in the form of `StreamOperation` objects, and provides them to your `NoSQLSubscriber` implementation for processing.	For an introduction to `NoSQLSubscription`, see Working with Subscriptions. The `StreamOperation` class is introduced in Using the StreamOperation Class. For more information on `NoSQLSubscription`, see NoSQLSubscription.

NoSQLPublisher

Aggregates table operations into a single stream, and publishes them according to the configuration received from its subscriber(s).

For any Java JVM, create only one NoSQLPublisher class instance for a publisher configuration. You can create multiple publishers per JVM, as long as their configurations differ. For example, you can create a single JVM to support two or more publishers, each connecting to different stores with their different configurations.

You can scale the streaming service to use multiple subscribers to stream events from Oracle NoSQL Database store.

NoSQLPublisher is introduced in the chapter titled Using a Streams Publisher.

For more information about scaling the streaming service to use multiple substribers, see Scaling a Streams Application.

For more information on NoSQLPublisher, see NoSQLPublisher.

NoSQLSubscriber

Interface that you must implement to define how to process each store operation, warning, and error. NoSQLPublisher manages each NoSQLSubscriber instance that you provide. The NoSQLPublisher can use multiple NoSQLSubscriber instances.

For an introduction to subscriber implementation, see Implementing Subscribers.

For information about how to use multiple subscribers streaming events from Oracle NoSQL Database store, see Scaling a Streams Application.

For more information on NoSQLSubscriber, see NoSQLSubscriber.

NoSQLSubscription

Represents a single subscription that you created. This class receives write and delete events present in the operations stream, in the form of StreamOperation objects, and provides them to your NoSQLSubscriber implementation for processing.

For an introduction to NoSQLSubscription, see Working with Subscriptions. The StreamOperation class is introduced in Using the StreamOperation Class.

For more information on NoSQLSubscription, see NoSQLSubscription.