|
Hello, Has anybody had any experiences with Axon.Ivy and NoSQL databases(namely, MongoDB) ? And if so, how did they approach it and what were the benefits/downsides of using NoSQL with Axon.Ivy. I know that Axon.Ivy Has some NoSQL functionality in it, but we are considering to use a more robust external database rather than relying on the internal one. For context, I have some experience in NoSQL and java, Namely in MongoDB using the Jongo driver. Anybody who has done java implementations is also welcome to share their knowledge. |
|
depends on the NoSQL approach you are heading for. Each NoSQL flavour has its distinct value. However, if you need a document storage (like MongoDB) I'd prefer the elasticSearch solution:
Is there any docs on elasticsearch within axon.ivy? i cant seem to find anything about it. The concept that works with ElasticSearch in the backend is called The main driver for using a document store are adaptive case management scenarios: https://developer.axonivy.com/doc/dev/designer-guide/concepts/adaptive-case-management.html#business-data-analytics ...so you may want to examine the features of caseMap driven processes as well. |
|
Update on this issue : We used the Jongo driver from here https://jongo.org/ to connect to MongoDB and use it as our application database. We used a repository model with Business Entities (rather than storing entire process business data) , and everything works fine. There were no strange behaviors and the application performs well. |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 25.10.2019 at 14:17
Seen: 1,610 times
Last updated: 21.11.2019 at 02:51
