Would you use Apache Cassandra for Camunda persistence?

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.

  • Orchestrating Cloud Events with Zeebe

    Disclaimer: This blog post is about Cloud-Native software, containers, Cloud Events, and Workflows. It describes a concrete example that you can run yourself using Kubernetes, Helm, and Zeebe.io. You should be familiar with Kubernetes and Helm to follow along and will learn about zeebe.io and cloudevents.io on your way. While working with Kubernetes the chances are quite high that you’ll find services written in different languages and using different technologies stacks. CloudEvents (cloudevents.io / CNCF spec) was born to enable these systems to exchange information by describing their events in a standard way, no matter which transports these services are using (HTTP, Messaging AMPQ/JMS, Protobuf, etc).  In such scenarios, where you have events being produced and consumed by different systems, there are common requirements that start to arise when...

    Read more
  • How we automatically keep our Documentation Screenshots...

    When you open the Camunda User Guide, you’ll see that there are many screenshots explaining the different functions and options the product offers. We hope that you, as a user, find those screenshots helpful. But for us as developers, creating and keeping those screenshots up to date has always been a pain. https://unsplash.com/photos/dDppsuM_UpE At the time of writing, the user guide for Camunda Optimize contained 94 screenshots. And with every release we add more functionality, which means the number of screenshots continuously grows. When we change the look of buttons or add a new section to the header, we need to update every screenshot that has a button or header in it. In practice, this meant we were manually recreating every...

    Read more
  • Git push to deploy to Camunda Cloud

    Using the Zeebe Action for GitHub, you can automate your GitHub repo to deploy BPMN models to Camunda Cloud when you push to a specific branch. In this quick tutorial, I show you how to configure your GitHub repo to deploy all BPMN models in the bpmn directory of your repo on a push to master. If you don’t have a Camunda Cloud account yet, you can join the public beta to get one. Create a client in Camunda Cloud Go into your Zeebe cluster in the Camunda Cloud console, and create a new client. You might want to name it “GitHub-Automation” so you know what it is for. Copy the “Connection Info” block by clicking the copy icon in the lower right-hand...

    Read more