Progress Sonic and Cape Clear blaze the SOA trail
Duelling ESB suites continue to advance on service-oriented integration, offering a choice between simple and affordable or sophisticated and costly
Click for larger view.
Debugging is pretty good, facilitated by a TCP/IP monitor, a Web service browser (to view running services), and fresh support for JMS and WS-Security. The data transformation tools, although decent, would benefit from an upgrade, as would the monitoring and management tools, although they're fine for sifting and sorting errant processes from log files.
One nice addition: Administrators can now hand-tweak a stalled process and replay failed activities during recovery rather than simply kick the process to the curb.
Cape Clear can be commended for the extra effort spent on bolstering support materials. Tutorials and samples in Studio help developers get going with the Eclipse IDE, with BPEL, and with services architectures in general. Although the tutorials are general, they stand out in contrast to the less-developed materials of Sonic Workbench.
In all, developer productivity, runtime performance, and transactional reliability all benefit from additions to this rev of the Cape Clear ESB. What's more, Cape Clear continues to deliver one of the easiest-to-use SOA platforms on the market today.
Progress Sonic ESB Product Family 7.5
Progress Sonic’s ESB suite has made impressive strides since I last visited the product. In addition to seeing the light of BPEL and adopting WS-ReliableMessaging, the company has extended an olive branch to developers by dumping the old Workbench. The new IDE greatly simplifies configuring, testing, and deploying processes and services, and it helps to mask a good deal of the complex SonicMQ underpinnings of the ESB.
Click for larger view.
The BPEL engine and event correlation have been well integrated with the ESB runtime and messaging. Progress Sonic’s ESB runs stand-alone within a JVM -- as opposed to those of Oracle and Cape Clear, for example, which require a J2EE application server -- and employs routing itineraries, which are manifests of routing logic that push processing across domains and clusters at runtime based on content and variable parameters.