|
Key to any enterprise IT backbone is an Enterprise Messaging
System (EMS), which encourages disparate applications to swap
semantically precise messages in a distributed, multi-platform,
multi-application domain. Care should be taken in selecting
an EMS, as not every one is created equal. Ideally, it should:
- Promote loose coupling of applications
- Impose as little overhead as possible so as not to become
a bottleneck
- Provide development tools such as code generators to
allow quick integration
- Work across a variety of application, OS, and hardware
domains
In the past, EMS products have supported CORBA, Java Messaging
Service (JMS) and Web Services. Each of these products presents
their own set of awkward limitations.
First, although CORBA boasts a multitude of advantages in
integration, it imposes a very heavy architecture requiring
conversion of everything to CORBA services. Next, JMS is lighter
weight and easier to implement than CORBA, however, fails
to support .NET and other Microsoft Windows environments.
Finally, Web Services by nature are RPC-based, but inflexible.
They do not allow tightly coupled applications to be integrated
properly nor offer real time operational capabilities.
NetZyme Universal Messaging Bus, the messaging backbone to
BizZyme Enterprise Services Bus (ESB), uses a different approach.
Ready to use, out-of-the-box solutions connect with all widely
used messaging systems. This approach minimizes the integration
effort, while accommodating a broad range of messaging services.
ESB’s are usually implemented as an abstraction layer
on top of EMS, and typically based on Web Services and XML
standards. BizZyme ESB is both standards-based and standards-independent;
hence, it can connect different standard communication layers,
regardless of protocol. BizZyme ESB is the only solution that
works in both Java and .NET environments out of the box, while
connecting all C/C++ based applications.
|
