OpenESB Frequently asked questions

Q: Why OpenESB means Open Extended Service Bus?

Answer: Originally, ESB meant Enterprise Service Bus, but today, OpenESB deals with many services beyond the enterprise scope, such as IoT, Big Data or Event Streaming.  OpenESB is not limited to enterprise services anymore. So OpenESB extends its scope and to reflect this evolution, it has been renamed “Open Extended Service Bus”.

Q: Why OpenESB means Open Extended Service Bus?

Answer: By design, we give capability the OpenESB bus to decide by himself at the runtime which service implementation must be chosen to provide the service. The decision process rule can be developed and deployed regarding your requirements. It is a far more advanced and sophisticated than the simple message flow management offered by the OpenESB competitor.

Q: What is the OpenESB history?

Answer: The company SeeBeyond started the OpenESB development in the middle of the 00’s. In 2005 Sun Microsystems bought SeeBeyond and added the product JavaCaps to its portfolio. Sun improved the product dramatically and put a part of its sources in open source to create the OpenESB project. In 2010, Oracle bought Sun Microsystems and cancelled its support for the project since it was a direct competitor of its products and at the same time, the OpenESB community has been created to overcome Oracle’s defection. Since 2010, the OpenESB community has supported and improved the project successfully.

Q: What is a difference between Glassfish and Standalone edition?

Answer: The first versions of OpenESB used the application server Glassfish as a container and took advantage of the Glassfish infrastructure (Cluster, JNDI, JDBC…). Nevertheless, OpenESB Glassfish did not match the new architecture such as the virtualisation and the cloud deployment. It forced the OpenESB users to add the Glassfish administration to their knowledge.  The community decided to remove the Glassfish server from OpenESB and designed a new OpenESB edition (named Standalone) with the main Glassfish features such as JNDI, directly implemented in the OpenESB core. Today OpenESB Glassfish is not supported anymore by the community, the users' feedback describes a standalone Edition 50 % faster than the Glassfish edition with 5 nine of reliability.

Q: Why OpenESB means Open Extended Service Bus?

Answer: Originally, ESB meant Enterprise Service Bus, but today, OpenESB deals with many services beyond the enterprise scope, such as IoT, Big Data or Event Streaming.  OpenESB is not limited to enterprise services anymore. So OpenESB extends its scope and to reflect this evolution, it has been renamed “Open Extended Service Bus”.  

Q: How scale OpenESB in the real projects?

Answer: OpenESB has been designed to provide natively strong horizontal scalability and every day on production; it proves its capability to scale. One of the bigger OpenESB user, a gaming player in Asia details the performance of its platform on production. The platform processes around 100 million of business process invocations daily (here we talk about complex business processes and not just HTTP requests) and generates around 10 billion of events, for analytic purposes.

Q: Why is JBI often associated with OpenESB?

Answer: JBI (Java Business Integration) is a Java specification issued in the mid 00’s. It describes a flexible and intelligent infrastructure for integration platform. OpenESB initial developments were based on this specification. This choice provided a strong, efficient and transparent organisation to OpenESB. It is the reason why, OpenESB is often associated with JBI.

Q: Do I have to learn JBI to use OpenESB?

Answer: No, JBI is only used to structure and organise the OpenESB developments. In no case, the user has to use or understand the JBI concept and in the same way, no one has to learn the thermodynamic to drive a car.