You are viewing an older version of this section. Click here to navigate to the latest version.

Choosing Between Flows, Patterns, or Services

Because of the emphasis on ease of use, simplicity, and flexibility that guided the creation of Mule 3, a number of choices are open at the outset.

Choosing Configuration Patterns and Flows

Take a look at configuration patterns and flows. These will allow you to go faster and further than you could using services alone. If you’re a new user, start first by looking at configuration patterns.

Mule 3 includes a number of configuration patterns designed to solve common integration problems with minimal XML. These patterns are similar to Enterprise Integration Patterns which are also widely supported in Mule but tackle bigger use cases, like creating a web service proxy. Take a moment to inspect the list of patterns.

If your project requires a more complex set of operations, you might want to consider flows, which are introduced in Mule 3.

For more information about patterns, read the Configuration Reference.

Choosing Services

Mule’s service-based architecture is well-suited for many scenarios where you are using Mule as a service container and exposing services over one or more endpoints. If you’re familiar with using previous versions of Mule, you can continue - with very few changes - doing things the same way.