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.
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:
- Why do you want to use Apache Cassandra and not a relational Database like PostgreSQL?
- Which parts of the process engine Api would you use with Cassandra? BPMN Workflow Execution, Task Management, History…?
- 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.
