Riding the Enterprise Service Bus
Here is to the perpetual problem of connecting disparate enterprise systems. Companies purchase or develop internally a variety of systems for different purposes: PLM, ERP, MES and all kinds of analytical and reporting systems. Supplier integrations just add to that pain.
All these systems must be integrated to ensure efficient distribution of information and elimination of all these dreaded data silos.
The options are either to build many direct bridges between systems, or implement the so-called Enterprise Service Bus (ESB) framework. While direct bridge setup costs are relatively low, they eventually create a very significant maintenance burden. Moreover, every new system introduced to the enterprise will require its own bridge – or bridges.
ESBs are more sophisticated and initially more expensive to implement, but they offer strategic advantages further down the road. They are designed to provide a uniform method for applications to connect to the bus and subscribe to messages based on simple structural and business policy rules. An enterprise service bus implements a communication system between mutually interacting software systems in a service-oriented architecture.
Needless to say, when we have a choice, we go for an ESB. Our principal tools are Apache Camel or JBoss, both being very advanced and battle-tested systems, with substantial developer community support.
If you are considering connecting your systems, please don’t hurry to build a bridge. Speak to us, and will help you to avoid that hungry troll.