Learn Deployment Models for Mule Applications
Learning Objectives
After completing this unit, you’ll be able to:
- Describe the main options for deploying Mule applications.
- Explain the benefits and considerations of each deployment model.
- Identify the role of Anypoint Runtime Manager in managing deployed applications.
Introduction to Deployment
When an API is ready to move from development into production, deployment becomes the next important step. Where and how you deploy affects how that API performs, how much it costs to operate, and how well it can meet the needs of your users.
Each organization has different requirements for availability, scalability, compliance, and control. Some teams need a fully managed platform that can scale quickly with minimal setup. Others prioritize control over infrastructure, especially when working within strict security or regulatory environments.
MuleSoft provides several deployment options to support these needs. In this unit, you learn about the main models available through Anypoint Platform and how each one achieves different business and technical goals. You also learn how Mule applications are managed after deployment using Anypoint Runtime Manager, MuleSoft’s centralized tool for monitoring and operations.
CloudHub Overview
CloudHub is MuleSoft’s fully managed, multitenant deployment platform. It provides a fast and reliable way to deploy Mule applications without needing to set up or maintain any infrastructure. The platform handles the operational details for you—routing requests, balancing traffic, logging activity, and adjusting capacity based on demand. Each application runs in its own secure environment, and you can manage everything through Anypoint Runtime Manager.
CloudHub: Who Should Use It
This model is a good fit for teams that want to launch applications quickly and focus on building integrations rather than managing servers. CloudHub is also designed for global availability, making it a strong choice for APIs that need to serve users across multiple regions.
CloudHub 2.0 Overview
CloudHub 2.0 is MuleSoft’s next-generation platform for deploying Mule applications. It builds on the foundation of CloudHub with a modern, container-based architecture designed for greater flexibility and resilience.
With CloudHub 2.0, each application runs in a dedicated container that can scale automatically and recover from failure. You can deploy multiple replicas of an application to increase availability or distribute traffic more efficiently. The platform also gives you more control over how resources are allocated to each app, making it easier to optimize for performance and cost.
CloudHub 2.0: Who Should Use It
This deployment model is well suited for enterprise teams that need high availability, regional control, or fine-tuned resource management. Like the original CloudHub, it’s fully managed and accessed through Anypoint Runtime Manager.
CloudHub Versus CloudHub 2.0
CloudHub 2.0 introduces a more flexible, container-based architecture that supports advanced scaling, high availability, and modern cloud practices.
However, CloudHub is still widely used and fully supported. Many teams continue to rely on it for its simplicity, stability, and ease of use.
Both options are available to meet different organizational needs—some teams prioritize speed and simplicity, while others need more control and customization.
Runtime Fabric Overview
Runtime Fabric is a deployment option for teams that want to run Mule applications in their own infrastructure. It supports cloud, on-premises, and hybrid environments, giving organizations more control over where and how their apps are hosted.
Unlike CloudHub and CloudHub 2.0, Runtime Fabric is customer-managed. That means your team is responsible for setting up and maintaining the infrastructure that runs your applications. In exchange, you gain more flexibility in how resources are configured, how traffic is routed, and how deployments align with internal policies and compliance needs.
Runtime Fabric: Who Should Use It
Runtime Fabric is well-suited for enterprises with strict security requirements, regional data regulations, or complex network topologies. Applications still run in containers and are managed through Anypoint Runtime Manager, but the runtime layer operates within your environment.
How to Choose the Right Deployment Model
Different deployment models offer different strengths. The best choice depends on what your team needs most—speed, control, flexibility, or compliance.
-
CloudHub is ideal for fast deployment without infrastructure overhead.
-
CloudHub 2.0 supports more advanced scaling and resilience while remaining fully managed.
-
Runtime Fabric gives you full control over where and how applications run, including on-premises.
Hosted Versus Customer-Managed Deployments
Every deployment model involves tradeoffs between control, responsibility, and ease of use. MuleSoft offers both hosted and customer-managed options to support different priorities.
In a hosted model like CloudHub or CloudHub 2.0, MuleSoft handles the underlying infrastructure. Your team focuses on building and deploying applications, while the platform manages uptime, scaling, patching, and security at the infrastructure level. This can accelerate delivery and reduce operational overhead.
In a customer-managed model like Runtime Fabric you take full ownership of where the applications run. That includes configuring the environment, maintaining infrastructure, and integrating with your existing systems. This approach allows for greater customization, tighter control over data and traffic, and alignment with specific compliance or network requirements.
Anypoint Runtime Manager
Runtime Manager is the centralized tool for monitoring and operating deployed applications. It provides a single view across environments, helping teams track performance, manage deployments, view logs, and configure alerts. You can also use it to restart applications, scale workers, or promote apps across environments like sandbox, staging, and production.
For teams using Runtime Fabric, Runtime Manager still plays a key role by connecting on-premises or cloud-hosted infrastructure to the broader Anypoint Platform. This helps ensure consistent governance and visibility, even in hybrid environments.
With Runtime Manager, teams can maintain control of their applications throughout the lifecycle—from deployment to day-to-day operations.
How It Works at Mule United Airport
At Mule United Airport (MUA), the development team has finished building a new API that shares real-time flight status information. The next step is to decide how to deploy it in a way that ensures reliability, performance, and security.
The MUA architect is reviewing the organization’s goals. The team wants the API to be highly available, easily scalable during peak travel periods, and secure enough to meet aviation industry compliance standards. The architect is also considering the technical expertise available. While the developers are strong on integration, they have limited resources for managing infrastructure.
CloudHub is appealing for its speed and simplicity. The team can deploy quickly without worrying about infrastructure setup. And the fully managed environment can keep operational tasks to a minimum. But Runtime Fabric offers more control and flexibility, which is important if the airport wants to integrate with internal systems or meet specific data residency requirements.
Meanwhile, the developers explore how Anypoint Runtime Manager can help monitor and manage the API once it’s live. They discover how they can use it to check logs, configure alerts for downtime or high error rates, and ensure the application meets service-level expectations.
Ultimately, MUA needs to weigh trade-offs between control and convenience. With a better understanding of the options, the team will be ready to make a choice that balances technical needs with business goals. The team decided to go with Runtime Fabric for its ability to monitor and manage Mule applications across different environments.
In this unit, you explored your options for deployment models. Next, examine how MuleSoft uses API proxies to separate implementation from access, giving you even more control over how your APIs are exposed and managed. And learn how MUA moved forward deploying their API.