Would you use Apache Cassandra for Camunda persistence?

By
  • Blog
  • >
  • Would you use Apache Cassandra for Camunda persistence?
TOPICS

30 Day Free Trial

Bring together legacy systems, RPA bots, microservices and more with Camunda

Sign Up for Camunda Content

Get the latest on Camunda features, events, top trends, and more.

TRENDING CONTENT
I am currently planning a hack session with people who are interested in using Apache Cassandra as database for Camunda Process engine.
Their main motivation for supporting us is that their whole application is running on Apache Cassandra and they want to use Cassandra as persistence provider for their workflows as well.
They have extensive experience with Cassandra and want to contribute their work as open source.

If the hacksession which will take place at the beginning of July is successful, we would setup a public repository on GitHub were the community could collaborate around this.

I have blogged about our friends at Zalando doing work in that direction as well.

Would more people be interested in being able to use Apache Cassandra as persistence provider for Camunda?
If true, maybe you can provide some feedback of the following questions:

  1. Why do you want to use Apache Cassandra and not a relational Database like PostgreSQL?
  2. Which parts of the process engine Api would you use with Cassandra? BPMN Workflow Execution, Task Management, History…?
  3. In which situations would you be willing to compromise on consistency?

If you have any comments on this, please get in touch with us by commenting here or pinging me on twitter @meyerdan.

Try All Features of Camunda

Related Content

We're streamlining Camunda product APIs, working towards a single REST API for many components, simplifying the learning curve and making installation easier.
Learn about our approach to migration from Camunda 7 to Camunda 8, and how we can help you achieve it as quickly and effectively as possible.
We've been working hard to reduce the job activation latency in Zeebe. Read on to take a peek under the hood at how we went about it and then verified success.