The following diagram illustrates how Adapter for Apache Cassandra processes adapter services at run time. 
Step | Description |
1 | An Integration Server client, typically using a flow or Java service, invokes a Adapter for Apache Cassandra service on Integration Server to perform an operation on a Apache Cassandra. You configured the adapter service earlier using Designer. |
2 | The adapter service gets a connection from the service's connection pool. Adapter connections contain connection information of Apache Cassandra. |
3 | The adapter service uses the DataStax Cassandra Client API to connect to Apache Cassandra. |
4 | All adapter services performs the CRUD operation against a data in Apache Cassandra.  For Insert, Delete, Update, and Query services, the adapter service performs the corresponding operation against the data in Apache Cassandra. |
5 | Depending on the adapter service type, such as a Query service, the adapter service may return data to Integration Server. If the operation is successful, the service returns the output from the Client jar API, if applicable.If the operation is unsuccessful, the service returns an error such as an Adapter Exception. If the Apache Cassandra throws an exception while performing the adapter service's operation, the adapter logs the exception in the Integration Server log. |