Camunda vs. InRule

Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.

Incentivized

With InRule, we are expecting to be able to move business logic out of the developer domain and back into the business domain. Business logic is currently captured in UI (data validation) and middleware layers. These are areas in any application where leveraging InRule's capabilities allow for changes in business logic to be made with little or no IT involvement.

• Asynchronous functionality of Camunda Platform and different types of gateways.

• It is easy to tweak business rule parameters.
• Create new logic with low barriers.

Incentivized

• Camunda expects that you will develop your own user interfaces. This is either a benefit or a barrier depending on your perspective on packaged UI.
• As an open source vendor, Camunda is under-covered in analyst reports.

• Needs more debugging capabilities.

Camunda provides pretty standard product support offerings.

InRule's Support Portal provides a "one stop shop" for submitting support questions, accessing training information, managing licenses, and getting updates on InRule's roadmap.

Lacks good documentation. Training and documentation is geared towards those who are already technically adept. Does not have as many data integrations as other full fledged products. Paid version of Camunda is not as fully fledged as other products.

Incentivized

InRule offers a more organized software design, a well-structured framework in design, and is easier for new users to start contributing given documentation. Drools is spreadsheet-based and lacking the capability to do really advanced pseudo-programming.

Incentivized

• The positive impact is that we are able to ensure the business process is being followed and that results in orders getting processed successfully leading to customer satisfaction and revenue
• Another positive impact is that we are able to track any anomalies and any errors in the order flow and retry them so that users don't have a negative experience.
• A negative point is that it is an overhead to maintain so there is significant engineering effort getting invested there

Incentivized

• It is always reliable and efficient.
• Has won customers over.