Article: Mule Implementation Patterns

Ideally, your Mule applications should exhibit the properties of any other well-architected software application: it should be easy to refactor and test, modular, and decoupled. It should also make some attempt to foresee future needs, making it easy to modify as requirements inevitably change. Mule can function anywhere from a one of integration applications to the central integration fabric for a Fortune 50 enterprise. Architecture of these applications, whether implicit or explicit, will impact their success.In this article based on chapter 7 of Mule in Action, Second Edition, the authors look at some patterns that simplify the implementation of these architectures.

Please enter the following information below to receive this content.
Email:
Name:

Where does my email address go?

Your address will get added to our general New Product Announcement list. We send email to this list about 4 times a month to announce new titles, present updates to our Early Access title list, and offer you special promotions and freebies. Our aim is that you will be able to rely upon us to provide information you can use to enhance your professional skills.

But what if you do not want to receive email from Manning? No worries! You will always find an opt-out link on our emails. We really do not want to bother you with any information you do not feel like receiving.

Enjoy the free content, and feel free to discuss or offer feedback to the authors in the Author Online!