Though some think SOA failed and others see it only as a partial success, this has been because of the approach to SOA and not its underlying principles. SOA (or what I’d rather call Service Orientation, but that doesn’t fit our obsession with TLAs) is responsible for beginning a new evolution in the way we build software. This change is as fundamental as the shift to OO programming but essentially a much bigger jump: OO was adopted one developer at a time, but SOA requires teams and departments to make the culture, technology, and mind shift together. Where SOA has been most successful is evolving the way we build applications to the point where new deployment models become possible; enter the cloud.
It’s been an exciting couple of months for MuleSource. We began the year with 2 blowout quarters behind us. Last week we announced that Mark Burton, the former executive vice president of Sales from MySQL has joined the MuleSource board of directors. Mark brings a wealth of sales operating experience from one of the most successful open source companies to date. Mark has an excellent understanding of the different sales dynamics an open source company faces and has an uncanny ability to communicate his ideas on sales operations and strategy that makes you wonder why you never thought of them yourself.
I recently wrote an article that appeared in eBizQ on the topic of SOA governance. In this article, I argue that the primary reason that many pundits have declared “SOA is dead” is that the traditional “top-down” approach to SOA and governance have failed. Vendors have for too long evangelized a “big bang” re-architecture of development processes, using their tools to enforce new behaviors from developers, in order to realize the benefits of SOA. These approaches have failed because they make the average developer’s life more difficult, rather than simpler. Development teams, already stretched for time and resources, are generally reluctant to do extra work in the pursuit of some abstract notion of “service reuse.” Instead, modern governance approaches that are getting traction today actually help developers by integrating with existing tools and streamlining, rather than obstructing, familiar processes.
If you missed last week’s webinar on Scalable SOA with GigaSpaces and Mule, you can catch it again in the archives. Uri Cohen from GigaSpaces did an excellent job demonstrating how easy it is to take services developed using Mule and make them highly-available and linearly scalable.
The demo application shown is also available. Download it and try it out. It shows how integrate GigaSpaces & Mule using an AJAX based web front end. You should have the following installed on your machine for the demo to work properly:
We’ve negotiated discounts for our blog readers and community members to get 35% off on Mule in Action by David Dossot and John D’Emic or Open Source ESBs in Action by Jos Dirksen and Tijs Rademakers. A few weeks ago, Andrew Perepelytsya blogged about these books, which you can now purchase on the Manning website. To take advantage of the discount, enter “msource35” during checkout.
Note that this approach is no longer recommended if you are using Mule 3.0.0 or later. Instead you can use the ObjectStore
. This allows use to store objects in memory, in a persistent store or across Mule HA clusters automatically. You can learn more about Mule 3.0 here
and download it here
Recently, there was a great question on one of the Mule mailing lists about where to store runtime data that can be used across the app. If you need to store runtime data that is available across your Mule application, you can store the data as objects in the Mule Registry. You can get a handle to the Registry from anywhere that you have access to the MuleContext, as in most Mule entities. For example, you could store the object as follows:
I am presenting a webinar with GigaSpaces tomorrow on Scalable SOA where we’ll be introducing a powerful joint solution integrating GigaSpaces’ XAP with the open source Mule ESB.
This webinar is intended for developers and architects looking for an end-to-end SOA solution, featuring application resiliency, failover and linear scalability
Today I released the 2.0 RC1 release of the Mule IDE. Not much changed since the last development snapshot but we have tested the IDE a lot internally on a variety of operating systems since then.
If you upgrade from a development snapshot, note that you’ll have to change the location of the update site: the snapshots were located under the snapshots distribution area but the new milestone release is located under http://dist.muleforge.org/mule-ide/updates/3.4/. Note that you have to create a new update site URL in order to install the release candidate.
Are you looking to integrate on-premise applications with on-demand applications, such as Salesforce.com?
Join me for a technical webinar on integrating Salesforce.com with Mule. During this 30-minute event, I will demonstrate how to take an enterprise application integration (EAI) data synchronization pattern and extend it to integrate with data in the cloud.
Tuesday, February 3rd 2009
9am PT / noon ET
Click here to register now!