We have been running Galaxy successfully on our in-house servers and laptops for demo purposes for some time now and decided that having a running image of Galaxy on Amazon’s EC2 was the next logical step. Galaxy in the cloud gives us the opportunity to expose a running instance to a much wider audience than might otherwise interact directly with the product.
We’re happy to announce the availability of the RESTpack connectors for Mule 2.2, which include support for Jersey, Abdera, and Restlet. In addition to supporting the latest Mule 2.2 codebase, the following improvements have been made:
- JERSEY-8: Filters and security are now correctly applied to endpoints.
- JERSEY-2: Endpoints are now synchronous by default
- Upgraded to the Jersey 1.0.2 release
- RESTLET-9: Restlet Request ChallengeResponse is not properly initialized (Guards now work correctly in Mule)
We are pleased to announce the General Availability of Mule Enterprise 2.2. This release includes all the great features and bug fixes in the latest Community Release and more. An evaluation of Mule Enterprise 2.2 can be downloaded, or existing customers can access it via the MuleSource Support Portal.
We are pleased to announce that the community release of Mule 2.2.1 is now available for download. This is a maintenance release for Mule 2.2 that includes several bug fixes for passing message properties between CXF endpoints, complex regular expressions in JDBC statements, ordering of events from the <correlation-resequencer-router/>, and more.
Are you currently using Mule or evaluating Mule for use with your WebSphere MQ messaging system? Do you need to utilize WebSphere MQ specific messaging headers, message types, and character code IDs with Mule? Would you like to know how to deploy Mule for maximum reliability when coupled with WebSphere MQ?
On Monday, I spoke to a standing room only crowd at the San Francisco Java Users Group about using the Mule ESB to integrate applications. We talked about:
- What Mule is and what is the difference between integration and SOA
- Why use a Mule for integration
- How Mule helps with integration in the Cloud
- Best practices for planning and implementation
- Test driven development with Mule
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.