Supported Configurations for Anypoint Platform PCE
To ensure platform performance, stability, and high availability, Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) supports two network configurations in Kubernetes (K8s) nodes: 4-node and 7-node.
Anypoint Platform PCE 4.1 Architecture
The diagram illustrates MuleSoft’s planes (control plane and runtime plane) and their general traffic flow within the Anypoint Platform PCE context:
Control plane:
-
A subset of Anypoint services is deployed in Kubernetes (customer’s choice - Anypoint Platform PCE v 4.0 supports RKE2, EKS-A, OpenShift).
-
This constitutes the MuleSoft Control Plane, a web-based management and administration tool for the lifecycle of MuleSoft integration apps and APIs.
-
Starting with Anypoint Platform PCE v4.0, use a dedicated Kubernetes control plane to separate cluster management components from customer workloads.
Runtime plane:
-
MuleSoft offers various runtime planes
-
Within Anypoint Platform PCE context, the test uses the Hybrid runtime plane to deploy and manage runtimes via the MuleSoft control plane.
The following recommendations and limits are based on these resources: * A small (4-node) environment consisting of 4 K8s worker nodes of 8 cores and 32GB RAM and 3 dedicated K8s control plane nodes, or * A large (7-node) environment consisting of 7 K8s worker nodes of 8 cores and 32GB RAM and 3 dedicated K8s control plane nodes
Mule Runtime Engine and Mule Applications
This table shows the recommended and maximum number of Mule instances and Mule applications that Anypoint Platform PCE supports:
| Description | Supported Capacity |
|---|---|
Maximum number of Mule instances per environment |
500 |
Maximum number of Mule instances across all environments |
4000 |
Maximum number of Mule instances per server group |
20 |
Maximum Mule instances per cluster |
8 |
Mule applications under management per environment (recommended) |
Under 200 |
Mule applications under management per environment (maximum) |
500 |
Mule applications per Mule runtime engine (recommended) |
Fewer than 25 |
Mule applications per Mule runtime engine (maximum) |
100 |
Number of Mule applications |
15000 |
Number of Mule application replicas. An application can run on multiple Mule instances in a server group or cluster. |
30000 |
APIs and API Manager
This table shows the maximum number of instances per API, number of client applications, applied policies, and created contracts that Anypoint Platform PCE supports:
| Description | Supported Capacity |
|---|---|
Maximum instances per API group |
100 |
Client applications (per user) |
5000 |
Client applications (per root organization) |
10000 |
Maximum API instances managed per root organization |
12000 |
Applied policies |
36000 |
Created contracts |
24000 |
Access Management
This table shows the maximum number of business groups and number of Access Management users that Anypoint Platform PCE supports:
| Description | Supported Capacity |
|---|---|
Maximum number of supported business groups |
75 |
Maximum number of users |
10000 |
Exchange
This table shows the maximum number of Exchange assets and file size information that Anypoint Platform PCE supports:
| Description | Supported Capacity |
|---|---|
Maximum Exchange assets |
60,000 |
Maximum file size when publishing asset through UI |
5 MB |
Maximum uncompressed file size |
50 MB |
Maximum file size when publishing asset through Maven |
200 MB |
Maximum number of dependencies for a single asset |
100 |
Maximum icon size |
2 MB |
Maximum number of resources (attachments) per asset portal |
100 |
Maximum resource size for attachments to the asset portal |
2 MB |
Maximum indexable asset content for RAML or asset portal |
1 MB |
Maximum number of categories per organization |
500 |
Maximum number of custom configurations per organization |
500 |
Maximum number of pages in a portal |
50 |
Maximum length of page name |
128 characters |
Maximum review title length |
30 characters |
Maximum review text length |
2048 characters |
API Designer and API Mocking Service
Maximum number of projects |
Limited by version control system |
Maximum number of concurrent users |
16 |
Maximum number of mocking service instances |
One per API version |
Maximum number of mocking service users |
16 |