By David Dossot and John D’Emic

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.

Mule Implementation Patterns (PDF)