Make sure you didn't miss anything with this list of the Best of the Week in the DevOps Zone (Apr. 4 to Apr. 10). This week's topics include the Heartbleed SSL bug, Continuous Delivery vs. Continuous Integration, two very different introductions to continuous delivery, and perfect test automation.
With Mule’s December release we introduced the new batch module. We received feedback about it and we even have some CloudHub users happily using it in production! However, we know that the journey of Batch has just begun and for the Early Access release of Mule 3.5 we added a bunch of improvements.
This article will outline the the basic control flow patterns as defined by vdAtHKB03. We will then analyze what patterns have limited support due to restrictions imposed by the BPMN2 process specification as detailed in BPM-06-22.
While developing flows with a recent Mule ESB there is a big chance you will make use of MEL in your configuration. Although this feature has added great benefits while developing Mule flows it sometimes drives me crazy.
This article covers a WSDL for a web service in which the target namespace and the service address were identical, and put a Mule web service proxy in front of the web service exposing the WSDL, not only the port address of the web service endpoint were rewritten, but also the target namespace.
The rabbit is out of the hat: I'm indeed working on a new book. It's called "RabbitMQ Essentials" and is published by PackT Publishing. Yes, you're reading right, after Mule, it's now RabbitMQ's turn! Clearly, I'm specializing in writing about animal-named technologies.
So microservices as they appear from Martin’s & James’s article is pretty much service orientation without some of the bad misconception that tied into the SOA moniker like WS*, ESBs as a must, etc., perhaps that’s a good enough reason for a new name but personally I doubt it.
Well, you probably know my thoughts on cloud, PaaS, iPaaS and the like. In short, there’s a lot of hype around it, unscrupulous vendors, and some awesome magic involved. But there is some truth to it when you live in reality.
In the previous part 3, we have seen how ActiveMQ helps distinguish remote consumers from local consumers which helps in determining shorter routes from message producers to consumers. In this part 4, we will look into how to load balance concurrent consumers on remote brokers.
So today on April 1st we released hawtio 1.3.0. Well we are likely not making the same headlines as others news would do on this Aprils fool day. But nevertheless it yet another sign of a great community and project where we release often.
In order to effectively use ActiveMQ, it is very important to understand how ActiveMQ manages memory and disk resources to handle non-persistent and persistent messages. ActiveMQ has three key parameters which need to be kept under check.
Without some understanding of the design choices, business value and developer marketing strategies, it can be very difficult to know where to start planning. The API Codex is designed to meet that exact need. We feature articles, videos and books created by industry experts in the field.
A Mule application which uses the Jboss TX transaction manager needs a persistent Object Store to hold the objects and states of the transactions being processed (further information about different object stores can be found in the following page). By default Mule uses the ShadowNoFileLockStorem, which uses the file system to store the objects.
Apache Camel is the most popular open-source integration library. You can implement complex routing, orchestration, transformation, and mediation with this library. With hundreds of connectors/adapters including those to common enterprise backends, it’s not difficult to see why it’s so popular.