Webhooks are a very simple way to tie application together on the Internet. Suppose application A wants to be informed when data changes in application B: the traditional approach consists in having application A poll B for changes. The webhooks approach turns the problem around: B gets configured so it hooks to A via HTTP calls. Whenever data changes in B (or for that matter, whenever anything of interest happens in B), B will call A to let it know. No more polling, just simple HTTP server-to-server callbacks. Webhooks is so simple that there is no spec for it: the HTTP spec is all what is needed really.
Category: Mule ESB
A new Mule release has to come with another internal hackathon. Our development teams focused on using the new features we added in Mule 3.3 and we came to the conclusion “A hackathon is like a box of chocolate, you never know what your are gonna get”. In our case, we got some really cool applications, so cool that some of those can become real products in the future.
We’ve just released Mule ESB 3.3 into the wild. This is a big release for us and and marks a huge step forward in the ease of use of Mule and what you should expect from an integration platfrom. Not only has Mule Studio been significantly improved and the brand new DataMapper added, but Mule itself has also undergone a number of significant improvements.
With the flexibility and power of Mule Flows introduced in Mule ESB 3.0 along with Mule Studio including DataMapper and the improvements to Mule itself in this new release, Mule ESB 3.3 really is “Mule 3 Reloaded”. Read the recent whole product release announcement for an overview of everything that is being released with Mule ESB 3.3, then continue reading this post to get the low down on some of the most important new feature in Mule.
Would you like chicken or pasta? Chocolate or vanilla? Coffee or tea? White wine or red? Component or transformer? If you have a piece of custom code, should you implement it as a custom transformer or as a custom component?
Technically, you can do either. But under what circumstances is it better to use a transformer versus a component?
With Mule Studio DataMapper, Cloud Connectors, new management functions and so much more, developing with Mule was made significantly simpler in the latest release. Join Albin Kjellin, MuleSoft Enterprise Architect, for a walkthrough of the new Mule in action.
This is a live action webinar: all demos, no slides.
The SOAP standard was created to address the communication needs between different applications independently of the programming language, platform or technology in use. It is a standardized protocol based on XML over a variety of communication protocols such as HTTP, to invoke methods on remote objects. In this blogpost we’re going to consume SOAP web services implemented with the Microsoft Windows Communication Foundation framework (WCF) from a Mule application. WCF is part of the .NET framework since version 3.0 and provides the building blocks to expose C# and VB.NET methods as SOAP web services, hosted on the IIS web server.
Today I am going to introduce you to some powerful new features in Mule 3.3:
Improved Error Handling: New exception strategy patterns fully integrated in Studio. Included are Try/Catch, Rollback processing and Conditional Exception processing in Choice routers based on exception type, or just about any criteria!
Iterative Processing using Foreach Scope: Allows for iterative loop type processing while maintaining the original message context
Mule Expression Language: A new, unified expression language to improve consistency and ease of use when validating, filtering, routing, or transforming messages
Cache: Improve performance with “In memory” caching of messages, such as the results of service calls
Graphical Data Mapper: A new graphical tool to easily transform from one data format to another data format while also mapping specific fields within the message structure. Formats supported include XML, JSON, CSV, POJOs, collections of POJOs, and EXCEL
I’m extremely happy to announce the General Availability of Mule ESB 3.3. We’ve poured months of concentrated effort into producing a new version of Mule that makes systems integration even easier and developers more productive.
This release introduces powerful application and data integration capabilities, and features dramatic improvements in developer productivity and enterprise-class performance and scalability. Combined with a significantly upgraded Mule Studio, Mule ESB 3.3 offers the most advanced ESB suite in the market for integrating on-premise, SaaS and custom applications.
In August 2011 the AMQP Working Group passed the reins to the newly formed OASIS AMQP Member Section. After being developed in a very pragmatic manner by a consortium of “financial service institutions, infrastructure providers, and integration, transaction and networking specialists” (sic), the AMQP protocol became a internationally recognized standard.
A few months later, the final version of the AMQP 1.0 protocol was published. Though it may seem like a tiny increment from the previous version (0-9-1), the latest version of the protocol actually went through some major changes. So let’s go for a quick rundown of these changes.
I was reading John D’Emic’s brilliant post Twitter Complex Event Processing (CEP) with Esper and Drools and got truly inspired. After playing around with the combination of Mule and Esper I was amazed how good they suit each other. Letting Mule do the hard work of shuffling data and intelligent routing while Esper analyzing events on a overall level. It gave me kind of a opportunity to be stateful in a stateless environment. For those who aren’t familiar with Esper, it is what is called a Complex Event Processing engine that allows you to create queries and assertions on streams of events in real-time.