ASF Grants Synapse Separate, Top-Level Project Billing

Even if the announcement that Apache Software Foundation (ASF) granted Synapse separate, top-level project billing last week didn't generate major waves of uproar of reaction and commentary, it remains a significant move to the overall state of a burgeoning open source SOA arena. Initially, after first catching wind of Synapse in early spring of last year, I was thrown off slightly by some of the divergent descriptions/understandings of the effort that were floating around the web and as is the case with incubated open source projects it was a rapidly changing code base looking to grow in a more concisely defined direction over time. Since this is normally the case with early stage open source efforts especially those that set out to tackle broad scale areas of competency like SOA...

...provided three main functions: managing virtualized connections, service management and message transformation. Previously, it was useful for exchanges made through SOAP-based Web services where management of the exchanges were available through the WS-* protocols. Now support has been extended to numerous open standards such as HTTP, SOAP, FTP, SMTP, XML, XSLT, XPath, JMS, Web Services Security (WSS), Web Services Reliable Messaging (WS-RM), and more.

BPM and SOA, Cordys style

The BPM market is going through a change process and many of the old categorises are no longer appropriate, as BPM products all provide support for application integration and human workflow. One of the key sales messages from BPM vendors is the relationship between SOA and BPM. Cordys have entered the BPM market with a version 2 product that not only provides BPM to support SOA, but is itself developed on SOA. At the beginning of December 2007, I met Jon Pyke, Chief Strategy Officer of Cordys, to be briefed on their product and strategy. For those of you who have been involved in BPM for sometime the name will be familiar.

The SOA Grid uses existing JMS-compliant messaging systems. It also provides content-based routing and message transformation through XSLT. It does not require a separate Java EE application server, but provides its own lightweight environment that requires only a JVM...

BPM and SOA, Cordys style

The BPM market is going through a change process and many of the old categorises are no longer appropriate, as BPM products all provide support for application integration and human workflow. One of the key sales messages from BPM vendors is the relationship between SOA and BPM. Cordys have entered the BPM market with a version 2 product that not only provides BPM to support SOA, but is itself developed on SOA. At the beginning of December 2007, I met Jon Pyke, Chief Strategy Officer of Cordys, to be briefed on their product and strategy. For those of you who have been involved in BPM for sometime the name will be familiar.

The SOA Grid uses existing JMS-compliant messaging systems. It also provides content-based routing and message transformation through XSLT . . .