running camunda with Spring boot & mongodb

user_1860089 0
Viewed 1669

Has anyone been able to get Camunda to run with Spring Boot and mongodb?

I tried several approaches and always got into a brick wall.

What I tried:

1. jpa / hibernate-ogm

I was able to initiate a connection to mongo after creating my own CamundaDatasourceConfiguration and ProcessEngineConfigurationImpl. It failed when Camunda tried to get table metadata. I couldn't plug out this behavior.

2. jdbc driver for mongo by progress

I set up the jdbc url and driver class by progress. Camunda then gets stuck during the startup process and does not get to the point where Jetty is fully started, i.e. the "Jetty started on port XYZ" message in the log.

3. camunda with postgres with mongo FDW

FDW is a mechanism for postress to interface an external datasource. This way an application can work with postgres over jdbc while the FDW will take care of reading and writing the date to the external source, be it a file, mongodb, etc.

After realizing 1 and 2 don't work, I started working on 3.

Has anyone succeeded in doing this and can share how?

postgres-fdw spring-boot camunda mongodb
1 Answers

so I ran into the same problem and decided to share my answers with you.

Currently it is not possible to run the Camunda-Engine with a NoSQL Database.

In this Camunda-Forum-Post one of the guys at Camunda also says it is not possible to run the engine completely without a database.

And in the offical Camunda-Docs there is also a list with all supported environments. Currently there are only SQL-Databases listed:

https://docs.camunda.org/manual/7.10/introduction/supported-environments/

But in some earlier Blog-Posts they metioned, that they want to make some proof-of-concept examples with the use of NoSQL-Databases. So we can expect, that these databases will be supported in the future, but not at the moment.

(note: the flowable engine is doing the same proof of concepts, they mentioned, that they want to be able to use NoSQL-databases by the end of the next year).

user_105133910
Related