Thursday, July 23, 2015

Calling Cassandra async from QBit using Reactor and CallBackBuilder, and Callbacks

Cassandra offers an async API as does QBit. Cassandra uses Google Guava. QBit uses QBit. :)
How do you combine them so you do not have to create a worker pool in QBit to make async calls to Cassandra?
Let's say you have a Cassandra service like so...

Example Cassandra service

import com.datastax.driver.core.*;
import com.google.common.util.concurrent.FutureCallback;
import com.google.common.util.concurrent.Futures;
import io.advantageous.qbit.annotation.*;

import java.util.Map.Entry;
import java.util.concurrent.atomic.AtomicBoolean;

import io.advantageous.qbit.reactive.Callback;

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import com.datastax.driver.core.exceptions.QueryExecutionException;
import com.datastax.driver.core.exceptions.QueryValidationException;

public class CassandraService {

    private final Logger logger = LoggerFactory.getLogger(CassandraService.class);
    private final CassandraCluster cluster ;
    private final CassandraConfig config;
    private final Session session; //only one per keyspace,
    private final AtomicBoolean isConnected = new AtomicBoolean(false);
     * Configure the client to connect to cluster
     * @param config
    public CassandraService (final CassandraConfig config) {


    public void executeAsync(final Callback<ResultSet> callback, final Statement stmt) {
        final ResultSetFuture future = this.session.executeAsync(stmt);

        Futures.addCallback(future, new FutureCallback<ResultSet>() {
            public void onSuccess(ResultSet result) {

            public void onFailure(Throwable t) {

Note that Futures from Cassandra driver support comes from the Guava library from google. DataStax has a nice tutorial on using Cassandra async API with Guava.
In this example we have a service called EventStorageService which endeavors to store an event into Cassandra. Most of the plumbing and tables DDL for the Event have been omitted. This is not a Cassandra tutorial by any means.
Note that in the onSuccess of the FutureCallback that we call the QBit callback akaCallback accept method. A QBit callback is a Java 8 consumer interface Callback<T> extends Consumer<T> which is probably what FutureCallback would have been if it were created post Java 8. You can also see that if theFutureCallback.onFailure gets called and that the code delegates to onError. Fairly simple.
Now we have another service call this service. As in this example CassandraService is a thin wrapper over the Cassandra API.

Example service that uses the cassandra service

public class EventStorageService {
    private final Logger logger = LoggerFactory.getLogger(EventStorageService.class);

    private final CassandraService cassandraService;

    private final Reactor reactor;

    public EventStorageService (final CassandraService cassandraService,
                                final Reactor reactor) {
        this.cassandraService = cassandraService;
        logger.info(" Event Storage Service is up ");

        if (reactor!=null) {
            this.reactor = reactor;
        } else {
            this.reactor = ReactorBuilder.reactorBuilder().build();


    @RequestMapping(value = "/event", method = RequestMethod.POST)
    public void addEventAsync (final Callback<Boolean> statusCallback, final Event event) {
        logger.debug("Storing Event  async {} " , event);
        final EventStorageRecord storageRec = EventConverter.toStorageRec(event);

        final Callback<ResultSet> callback = reactor.callbackBuilder()
                .setCallback(ResultSet.class, resultSet -> 
                .setOnTimeout(() -> statusCallback.accept(false))
                .setOnError(error -> statusCallback.onError(error))

        this.addEventStorageRecordAsync(callback, storageRec);


    public void addEventStorageRecordAsync (final Callback<ResultSet> callback, 
                                            final EventStorageRecord storageRec) {
        logger.info("Storing  the record with storage-key {} async  ", storageRec.getStorageKey());

        if(storageRec != null) {

            SimpleStatement simpleStatement = ...;
            cassandraService.executeAsync(callback, simpleStatement);



Note that QBit uses a callbackBuilder so the constituent parts of a callback can be lambda expressions.
Callback is a rather simple interface that builds on Java 8 Consumer and adds timeout and error handling.


public interface Callback<T> extends Consumer<T> {

    default void onError(Throwable error) {

                .error(error.getMessage(), error);

    default void onTimeout() {


The Reactor is class to manage timeouts, schedule periodic tasks, and other service call coordination. We initialize the Reactor in the constructor of theEventStorageService as seen in the previous code listing. We use thecallbackBuilder created from the Reactor as it will register the callbacks with thereactor for timeouts and such.
To enable the reactor, we must call it from service queue callback method of idle, limit and empty. One merely needs to call reactor.process from the callback, and it will periodically check for timeouts and such.

Calling reactor process to process callbacks and handle timeouts

    public void process() {

Underneath the covers.

The Reactor uses AsyncFutureCallback which is both a FutureRunnable and aCallback so therefore a Consumer. Rather then invent our own async API or functional API we decided to lean on Java 8, and build on the shoulders of giants.

Reactor uses AsyncFutureCallback internally. And CallBack builder really builds AsyncFutureCallback

public interface AsyncFutureCallback<T> extends Runnable, Callback<T>, Future<T> {
    Exception CANCEL = new Exception("Cancelled RunnableCallback");

    boolean checkTimeOut(long now);

    void accept(T t);

    void onError(Throwable error);

    void run();

    boolean cancel(boolean mayInterruptIfRunning);

    boolean isCancelled();

    boolean isDone();

    T get();

    T get(long timeout, TimeUnit unit);

    default boolean timedOut(long now) {

        return !(startTime() == -1 || timeOutDuration() == -1) && (now - startTime()) > timeOutDuration();

    default long timeOutDuration() {
        return -1;

    default long startTime() {
        return -1;

    default void finished() {


    default boolean isTimedOut() {
        return false;

No comments:

Post a Comment

Kafka and Cassandra support, training for AWS EC2 Cassandra 3.0 Training