Circuit Breaker is a pattern that wraps the resource and monitors for errors. Initially it is in closed state and passes all calls to the wrapped resource. When the failures reaches a certain threshold, the circuit moves to open state where it returns error to the caller without actually calling the wrapped resource.
A common integration scenario is a single message needs to be sent through multiple routes.
It needs to be routed through the CRM to create the client, to marketing for leads, and finally passed to provisioning and stock systems so they can work their magic as well.
We've just released the v2.2.0 of the UltraESB. The release fixes some defects related to classloading from deployment units, and also introduces a few changes to the public API to make the ESB API more user friendly and intuitive.
In this article, I’m going to outline the importance or addressing your company’s source-control use before diving too far into CD. Specifically, I’m suggesting that you should decide whether your enterprise should do Trunk Based Development (TBD) in one big trunk or not.
There was considerable interest in the MQTT interop session on standardizing the use of OAuth2 tokens with the protocol. My personal prediction is that MQTT and HTTP become the most-used IoT protocols, and I strongly urge (and hope) that OAuth2 tokens will become the de-facto model across both of these.
For a long time I thought that was impossible to query the SOA composite instance audit trail directly from database. Several references on internet said that only SOA Management APIs could understand the format in which this information is stored into SOA Dehydration Store.
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.