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.

About john.demic

John D'Emic has written 11 post in this blog.

John is a technologist, developer and author. His specialties include Integration, Java, Mule, MongoDB, Groovy, Grails, Javascript, Spring, Spring Roo, Hibernate, Hibernate Search / Lucene, Geospatial, iOS, JMS, HornetQ, Unix, Linux, LDAP, and Sendmail.

No related posts.


One Response to “Cheat Sheet: Asynchronous Message Processing”

Scott Banwart's Blog › Distributed Weekly 192 February 1st, 2013, 1:35 am

[...] Cheat Sheet: Asynchronous Message Processing [...]

Leave a Comment