Nav
You are viewing an older version of this topic. To go to a different version, use the version menu at the upper-right. +

Mule App Deployment Model

A Mule Project for deployment is a Mule Application. A Mule runtime instance supports multiple applications running independently within the same Mule container. This allows additional advantages such as:

  • Running multiple applications side-by-side

  • Clear boundaries for operations on what a Mule application is

  • Mule can monitor your applications and will reload configuration changes automatically

  • Applications can depend on different library versions, even if they would conflict before

  • Multiple versions of an application can exist side by side

Every application is deployed together within a domain. By default, your application references the default domain, and no further configuration is required. You can see that it gets deployed together with the app in the console:

deploy+domain

If you’re deploying multiple applications to the same place, and those applications could share the same resources, then you can create a common domain where you can define common configurations that can then be referenced by multiple projects. This allows you to, for example, expose different services in different projects through the same HTTP host and port and be able to deploy everything without any conflicts. Read More.

Understanding the deployment model can be divided into several topics:

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.

+