Contact Free trial Login

Anypoint Runtime Fabric Overview

Anypoint Runtime Fabric is a container service that allows you to run Mule applications, composite APIs and API gateways across any environment with centralized management via Anypoint Platform.

Some of the capabilities of Anypoint Runtime Fabric include:

  • Isolation between applications by running a separate Mule runtime server per application.

  • Ability to run multiple versions of Mule runtime server on the same set of resources.

  • Scaling applications across multiple replicas.

  • Automated application fail-over.

  • Application management with Anypoint Runtime Manager.

Contact your customer success manager for information on how to enable Anypoint Runtime Fabric on your account.

There are two management options for Anypoint Runtime Fabric:

  • Runtime Fabric on Self-Managed Kubernetes: a version of Runtime Fabric that you install on an existing Kubernetes environment that you operate and manage. This version supports Amazon Elastic Kubernetes Service (Amazon EKS), Azure Kubernetes Service (AKS), and Google Kubernetes Engine (GKE).

  • Runtime Fabric on VMs / Bare Metal: a version of Runtime Fabric where MuleSoft provides required software infrastructure components, including Docker and Kubernetes. You install this version on virtual machines that you operate and manage.

Each of these options has its own system requirements and installation procedures. See Runtime Fabric on Self-Managed Kubernetes and Anypoint Runtime Fabric on VMs / Bare Metal for more information on each option.

Table 1. Personas required to install and support Anypoint Runtime Fabric
Runtime Fabric Option IT Administrator MuleSoft Organization Administrator

Self-Managed Kubernetes

Requires an IT administrator to create and configure a Kubernetes cluster on Amazon EKS, AKS, or GKE. This persona is also responsible for installing Runtime Fabric and managing Kubernetes.

Creates Runtime Fabric instances, deploys applications, and performs other tasks within Anypoint Platform

VMs/Bare Metal

Creates and configures the infrastructure that runs Runtime Fabric. This persona is also responsible for installing Runtime Fabric and maintaining the underlying infrastructure during its operation.

Creates Runtime Fabric instances, deploys applications, and performs other tasks within Anypoint Platform

Feature Support Matrix for Runtime Fabric on Self-Managed Kubernetes and Runtime Fabric on VMs / Bare Metal

Table 2. Supported features for Runtime Fabric on Self-Managed Kubernetes and Runtime Fabric on VMs / Bare Metal
Runtime Fabric on Self-Managed Kubernetes Runtime Fabric on VMs / Bare Metal

Support for deploying Mules and API Gateways

Supported

Supported

Kubernetes and Docker

Not included.
Provide your instances of Kubernetes and Docker via Amazon EKS, AKS or GKE clusters.

Included

Installing on any Linux distribution

Supported

Support for RHEL and CentOS only

Node auto-scaling

Supported using AWS, Azure or Google Cloud functionality

Not supported

External log forwarding

You must provide an external log forwarding service

Included

Internal load balancer

You must provide an internal load balancer (Ingress Controller)

Included

Anypoint Security Edge

Not supported

Supported

Ops Center

Not Included
You can enable monitoring and alerting in AWS, Azure, or Google Cloud

Included

Anypoint Runtime Fabric and Standalone Mule Runtimes (Hybrid Deployments)

Hybrid deployments of Mule applications require you to install a version of the Mule runtime on a server and deploy one or more applications on the server. Each application shares the Mule runtime server and the resources allocated to it. Other resources such as certificates or database connections may also be shared using domains.

Anypoint Runtime Fabric provisions resources differently. Each Mule application and API gateway runs within its own Mule runtime and in its own container. The resources available to the container are specified when deploying a Mule application or API proxy. This enables Mule applications to horizontally scale across nodes without relying on other dependencies. It also ensures that different applications do not compete with each other for resources on the same node.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub