Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Reuse and investment protection also results from the adherence to standards. Not only can developers swap out ESB components, or use components in another JBI-standard ESB, but they can swap out the entire ESB and still use the standard plug-in components.

SM allows plug-in services which can combine to create
a service oriented architecture. SM allows these services to
operate in an event driven way as well. In other words, the services
are decoupled and listen on the bus for service requests. The
bus is responsible for quality of service (QoS) features such
as message persistence, guaranteed delivery, failure handling,
and transaction support.

SM supports event driven architecture for events occurring
both internal and external to the bus. In other words, JMS binding
components can listen for the arrival of messages, i.e., the "event"
on topics or queues which are external to the bus, while other
binding components and service engine components can listen for
messages on the bus.

While decoupled operation (as described in the previous two paragraphs) is more
appropriate for the scalability and reliabilty required for
high transaction production environments, synchrounous request/response
communication found in early SOA implementations, is also supported.
Therefore, ServiceMix effectively combines SOA and EDA for
the development and deployment of composite enterprise applications.

Please see Background to ServiceMix for the philosophy behind the development of ServiceMix.

...