Hello Everyone ,
We have our Application Database in which defining data or configuration data is used. The defining data/configuration data is spread across many tables in database. Considering our domain i.e. Insurance , defining data and configuration data is huge in size.
We are exploring possibility of storing this data in Camunda in form of decision tables.
As of now , we already have such solution used for 1 usecase wherein UnderWriting questions/answeres are defined in Camunda decision tables and frontend application fetches questions and possible set of answers dynamically from Camunda using Camunda REST API.
We would like to know if such a solution worth implementing when data is huge and data objects are having relationships with other data objects.
Any inputs or feedbacks would be helpful. Let us know if more details are required.
Thank you.
Regards
Ketan