Answers to: NoSQL In Axon.Ivy

Answer by TareqK

TareqK — Thu, 21 Nov 2019 02:51:38 -0500

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.

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Mon, 28 Oct 2019 08:30:20 -0400

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.

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Mon, 28 Oct 2019 08:26:30 -0400

The concept that works with ElasticSearch in the backend is called BusinessData in axon-ivy. Be aware that the docs do not focus much on the technology but on features: https://developer.axonivy.com/doc/latest/DesignerGuideHtml/ivy.datamodeling.html#ivy-businessdata

Comment by TareqK on Reguel Wermelinger's answer

TareqK — Mon, 28 Oct 2019 06:49:21 -0400

Is there any docs on elasticsearch within axon.ivy? i cant seem to find anything about it.

Answer by Reguel Wermelinger

Reguel Wermelinger — Mon, 28 Oct 2019 05:32:00 -0400

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:

Monitoring: intertwined with the EngineCockpit, Logs, JMX... ElasticSearch is easy to handle in combination with Axon.ivy
API: simple repository centred API with nice update mechanisms (actually inspired by Mongo DB concepts)