Versions Compared

Old Version 4

changes.mady.by.user Unknown User (rich.petersen@logicblaze.com)

Saved on

compared with

New Version 5

changes.mady.by.user Unknown User (rich.petersen@logicblaze.com)

Saved on

Key

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

...

This project (Synapse) is related to ESB, but it is not in itself an ESB. What Synapse brings to the table is a mediation framework that allows users to get in the middle between service requesters and providers and perform various tasks including transformation and routing and that helps to promote loose coupling between services

 

The distinction David makes goes to the heart of both questions. First, Synapse is not a full ESB in the most common sense of the term. Secondly, because the design of Apache Synapse is different from that of Apache ServiceMix, the two solutions have different capabilities and limitations.

...

  • that all exchanges in the SOA would be Web Service exchanges based on SOAP,
  • that the management of the exchanges would be invoked exclusively by means of WS-*
  • that the underlying SOAP technology at each brokered endpoint would be Apache AxisAxis2.

ServiceMix is a full ESB that can work with many different SOAP Stacks such as Axis, WSIF, XFire, ActiveSOAP and JAX-WS. ServiceMix also has full support for Routing, Transformation and Orchestration. Like Apache Synapse, Apache ServiceMix provides mediation for web services exchanges and is designed to support transformation, management and routing through WS-* standards. However, this capability is provided independently of the SOAP stack, and most importantly, is provided through the same services architecture used for all message formats and transports, including, but certainly not limited to, Web services.

...