Hi! I’m looking for some pointers in the Camunda documentation or other resources to help us on this transformation journey.
Our web application, with its classic application server + database server, is due for an overhaul. We will not be making many changes to our UI, but we are looking to untangle all the business logic that is tightly coupled within the application server and turn all that logic into a readable and maintainable set of processes.
We would like to “plug-in” Camunda and let Camunda make changes to the DB (update, delete and create records), trigger emails, notifications, etc. Is Camunda able to listen, consume and generate events, using AWS SQS/SNS for example? Should we let Camunda listen to specific DB changes to cause it to trigger? Or should all of it be called via Rest APIs, whether it is the application passing information to Camunda or vice-versa?
What are the best patterns when it comes to plugging in the Camunda engine into a custom application, causing it to trigger, then execute a set of business rules, followed by notifications to users, changes to the DB?
Thank you,
Milos