InRule vs. WSO2 Integration Platform

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.

The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.

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

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• Service chain pattern
• Message transformation
• Call more than one backend service
• Call service with different protocoll as the client use
• Use file as input
• Use mail as input

• Needs more debugging capabilities.

• View deploy artifact in date time order
• Easy way to map data
• Easy way to manage payload

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.

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

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.

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

• Reduce development time to the service integration
• We can use junior developer
• Clustered in easy way