You want to get more done in 2013 so you’re going to need to switch from synchronous to asynchronous processing to do more with the same resources. Mule started life as an asynchronous message engine and has a lot of capabilities and optimisations built in for processing data concurrently. To help you understand asynchronous processing in Mule we have created this cheat sheet that will help you understand the basics. Feel free to ask questions on this blog or on the forums. Enjoy.
Tag: Mule 3
One of our New Year resolutions is to create more content around specific subject areas. The aim of MuleSoft Blueprints is to provide a complete guide on a specific topic in a way that can be easily read and kept for reference.
To get you started we have a preview of the Load Balancing Mule for Availability and Scalability. This blueprint will introduce the necessary concepts and show how to achieve availability and scale with JMS, Mule HA, VM queues and more. This is a preview, we’d love to get your feedback on format, content and topics, you can reach us in the forums or just comment on this post.
Its good to connect and while we can’t help you get your cousin Billy to look up from his Nintendo 3DS we can help you connect to all the applications you use on the Web and a in the Enterprise. APIs are common language of the web and the New Enterprise and this book is the perfect guide to get your applications talking to each other. With the number of open APIs reaching over 13,000 this year according to APIhub, 2013 will all be about how developers orchestrate APIs to create applications. Mule Cloud Connect is here to help. Ryan Carter has done an excellent job of covering the subject in depth in his forthcoming O’Reilly book, Getting Started with Mule Cloud Connect. Here are the first 2 chapters to get you started.
Just a quick one today since you’re probably busy getting ready for the New Year (or clearing out your bunker after the world didn’t end on Christmas Eve as they Mayans predicated). Either way we recommend that you go download and print the Mule 3 Refcard from DZone. If you haven’t seen these reference cards before they are a great companion for working with many open source and commercial platforms. Th Mule 3.3 Refcard will guide you through the basics as well as provide examples for working with components , filters, annotations and exception handling. You can get yours here.
You’re going to read more in 2013, right? Well lets get you started with this sample chapter, Implementation Patterns in Mule from the forthcoming Mule in Action book from Manning Publishing. This book is the ultimate companion for anyone using Mule and Manning run an early access program so you get get you hands on 8 chapters currently and even pre-order the book. Enjoy!
We are making this release of Studio available to the Mule community to get valuable feedback on our latest and greatest features. This blog post contains text and video introductions to the freshly-baked features included in this release.
As you read through this post and try the Studio features, please keep in mind that this is a pre-Beta version. Explore, discover and play, but do not use it to develop Mule apps for use in production.
But there are a lot of use cases where this kind of cross domain HTTP request is desired, so developers came up with some workarounds:
- Server side proxy: the idea is to avoid cross domain requests in the browser by doing them on the server:To do that in Mule you can use the HTTP proxy pattern as explained in this post.
A frequent issue I come across writing integration applications with Mule is deciding how to communicate back and forth between my front end application, typically a web or mobile application, and a flow hosted on Mule.
I could use web services and do something like annotate a component with JAX-RS and expose this out over HTTP. This is potentially overkill, particularly if I only want to host a few methods, the methods are asynchronous or I don’t want to deal with the overhead of HTTP. It also could be a lot of extra effort if the only consumers of the API, at least initially, are internal facing applications.
Today I would like to talk a little bit about releasing a new version of your Mule extensions. As you may know Mule is a an extensible platform with well defined integration points for plugging in your own connectors transformations, components and even routers. Suppose you have used The Mule Devkit to create your very own extension or cloud connector, and your project is so cool that it was accepted on MuleForge.
What happens if you make changes to you project and it moves from version 1.0 to 1.1? We’ll take a very quick look at how to do that in this post.
First, modify your pom.xml to increase your version number. In this case, we’ll go from 1.0 to 1.1: