The process-oriented solution allows you to define choreography and orchestration. This feature makes it stand out against competitors such as WSO2.

The solution is contract-based which allows for the selection of services and implementation options based on the customer's needs. 

The most valuable features are :
- The full-service orientation of the product.
- The development process supported, from beginning to end, by a set of graphical development tools.
- The service composition is the core of the product and allows the developer to compose services in a very easy way. Similar to the Oracle SOA Suite composition, The OpenESB composition implements more additional features such as the connection policies between services and interface support. For example, the "last deployed" policy allows you to deploy a new version of service and automatically reroute the messages to this new version. If a bug appears, just redeploy the previous version. So you don't need to stop and start OpenESB and increase the platform availability.

The independence from the protocol invoking the services from it's implementation, making it possible to invoke the same service using different protocols (HTTP/FTP/JMS/FILE) and also being invoked directly inside the BUS without any additional protocol.

Last year I also began to use the Enterprise Version, and the out of the box integration with ELK form both technical and business monitoring. It is amazing.

Technical monitoring allows you how to build an amazing ELK dashboard, out of the box with information on time-response, request content, activity response time, etc.