Study guide
1.3 Anypoint Platform Architecture & Core Components
Salesforce Certified MuleSoft Developer I Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Creating Application Networks & API-Led Connectivity
1.1 The IT Delivery Gap & API-Led Connectivity Architecture 1.2 Application Network Foundations & Center for Enablement (C4E) 1.3 Anypoint Platform Architecture & Core Components
2 Chapter 2: Designing APIs with RAML & API Designer
2.1 RAML 1.0 Fundamentals, Data Types & Resource Hierarchy 2.2 Reusable API Fragments, ResourceTypes & Traits 2.3 API Mocking Service, Documentation & Anypoint Exchange Publishing
3 Chapter 3: Accessing and Modifying Mule Events
3.1 Mule 4 Event Architecture: Message, Payload, Attributes & Variables 3.2 Flow Variable Management & Target Variables Pattern 3.3 Accessing Event Metadata, Inbound Attributes & Context Properties
4 Chapter 4: Structuring Mule Applications
4.1 Modular Flow Composition: Flows, Subflows & Private Flows 4.2 Configuration Property Files & Environment Management 4.3 Secure Properties Tool, Encryption & Maven Project Packaging
5 Chapter 5: Building API Implementation Interfaces
5.1 APIkit Scaffolding, Router Configuration & Interface Generation 5.2 HTTP Listener Configuration, Path Matching & Query/URI Parameters 5.3 Interface vs. Implementation Separation & Backend Flow Wiring
6 Chapter 6: Using Connectors & External Systems
6.1 Database Connector: Select, Insert, Update, Stored Procedures & Watermarking 6.2 HTTP Request Connector: Headers, Query Params, Response Timeouts & Target Variables 6.3 Salesforce Connector, JMS Messaging & File/FTP Connectors
7 Chapter 7: Processing Records & Batch Integration
7.1 For Each Scope: Payload Iteration, Batch Size & Streaming Data 7.2 Batch Job Architecture: Input, Process, and Complete Phases 7.3 Batch Step Accept Expression, Failure Handling & Batch Aggregator 7.4 Object Store: Persisting Data Between Flow Executions
8 Chapter 8: Transforming Data with DataWeave 2.0
8.1 DataWeave 2.0 Syntax, Type System & Selectors 8.2 Core Functions: map, filter, pluck, reduce, groupBy & orderBy 8.3 Custom Functions, Format Transformations & Type Coercion 8.4 Calling Mule Flows from DataWeave & Reusing DataWeave Modules
9 Chapter 9: Routing Events & Flow Control
9.1 Choice Router: Conditional Expressions & Default Routing 9.2 Scatter-Gather Router: Parallel Execution, Aggregation & Error Traps 9.3 Async Scope, Round Robin & First Successful Routing 9.4 Validating Mule Events with the Validation Module
10 Chapter 10: Handling Errors & Exception Management
10.1 Mule 4 Error Object Hierarchy & Custom Error Types 10.2 On-Error Continue vs. On-Error Propagate Mechanisms 10.3 Try Scope Exception Isolation & Global Error Handling Strategies
11 Chapter 11: Debugging and Troubleshooting Mule Applications
11.1 Logger Configuration, Categories & Thread/Context Diagnostics 11.2 Anypoint Studio Debugger: Breakpoints, Expression Watches & Step-Through 11.3 MUnit 2.x Testing: Unit Tests, Mocking Connectors & Assertions
12 Chapter 12: Deploying and Managing APIs and Integrations
12.1 CloudHub 1.0 & 2.0 Architecture: Workers, vCores & Clustering 12.2 Runtime Manager: Application Management, Alerts, Insights & Logs 12.3 API Manager: Auto-Discovery, API Gateway, SLA Tiers & Standard Policies
1.3 Anypoint Platform Architecture & Core Components
Key Takeaways Explain This Topic AI
Anypoint Platform is divided into two distinct architectural planes: the Control Plane (designing, cataloging, managing, and monitoring APIs) and the Runtime Plane (executing Mule applications and processing transaction payloads).
MuleSoft offers four primary runtime deployment models: CloudHub 1.0 (managed AWS EC2 worker VMs), CloudHub 2.0 (managed containerized Kubernetes in shared/private spaces), Runtime Fabric (customer-managed Kubernetes), and Customer-Hosted Standalone Mule Runtimes .
Anypoint API Manager enforces runtime security policies (Rate Limiting, Client ID Enforcement, JWT Validation) and SLA tiers via API Autodiscovery without modifying underlying application code.
Anypoint Exchange is the central asset repository that provides self-service discoverability, interactive API documentation, simulated mocking endpoints, and reusable RAML/OAS fragments.
Anypoint Visualizer and Anypoint Monitoring utilize distributed telemetry from Mule runtimes to construct live architectural topology maps, performance dashboards, and real-time operational alerts.
Last updated: August 2026
Anypoint Platform Architecture & Core Components
MuleSoft's Anypoint Platform is a unified, multi-tenant integration and API platform delivered as a hybrid software-as-a-service (SaaS) suite. It provides end-to-end tooling across the complete API lifecycle, from design and testing to deployment, management, and operational analytics. To build, deploy, and govern enterprise applications effectively, developers must understand the architectural separation between the Control Plane and the Runtime Plane , as well as the specialized roles of core platform components.
1. Unified Architecture: Control Plane vs. Runtime Plane
Anypoint Platform utilizes a decoupled architecture that separates platform administration and lifecycle tooling from the runtime execution engine. +-----------------------------------------------------------------------------------------+
- | ANYPOINT PLATFORM UNIFIED ARCHITECTURE |
- | |
- | +=================================================================================+ |
- | | CONTROL PLANE (Hosted in Cloud: US, EU, Hyperforce, or GovCloud) | |
- | | - Design Center (API Designer) - Anypoint Exchange (Asset Catalog) | |
- | | - API Manager (Policies & SLAs) - Runtime Manager (Deployment Control) | |
- | | - Access Management (RBAC & Orgs) - Anypoint Monitoring & Visualizer | |
- | +=================================================================================+ |
- | | | | |
- | [Metadata / Deployment API] [Policy Sync via Autodiscovery] [Telemetry & Logs] |
- | | | | |
- | v v v |
- | +=================================================================================+ |
- | | RUNTIME PLANE (Executes Mule Runtimes & Processes Transaction Payloads) | |
- | | | |
- | | [CloudHub 1.0] [CloudHub 2.0] [Runtime Fabric] [Customer-Hosted] |
- | | (AWS Worker VMs) (Containers / K8s) (Customer K8s) (Bare-Metal/VMs) |
- | +=================================================================================+ |
- | | | | |
- | v v v |
- | [SAP / ERP Data] [Salesforce CRM] [Enterprise DBs] |
- +-----------------------------------------------------------------------------------------+
The Control Plane:
Functionality: Provides web-based interfaces and management APIs for designing API specifications, cataloging reusable assets, configuring security policies, deploying applications, managing access control, and analyzing runtime metrics.
Deployment Regions: Available as a multi-tenant cloud service in the United States (US), European Union (Frankfurt / EU), Hyperforce regions (Australia, Japan, UK), and dedicated Government Cloud.
Data Sovereignty Guarantee: The Control Plane handles only application metadata, configuration definitions, and telemetry metrics. Customer business data and payload contents never flow through or persist in the Control Plane.
The Runtime Plane:
Functionality: The distributed execution environment where the Mule Runtime Engine runs deployed integration applications, executes DataWeave transformations, communicates with backend systems, and processes business payloads.
Location Flexibility: Can be hosted in MuleSoft-managed cloud environments (CloudHub 1.0/2.0) or customer-managed environments (Runtime Fabric on Kubernetes, or on-premises virtual machines).
2. Runtime Plane Deployment Models Comparison
MuleSoft provides four distinct deployment models for the Runtime Plane to accommodate diverse regulatory, compliance, and infrastructure requirements: +-----------------------------------------------------------------------------------------+
- | RUNTIME PLANE DEPLOYMENT MODELS |
- | |
- | 1. CloudHub 1.0: Dedicated AWS EC2 Worker VMs managed fully by MuleSoft |
- | 2. CloudHub 2.0: Lightweight Kubernetes containerized replicas in Shared/Private Space|
- | 3. Runtime Fabric (RTF): Containerized Mule runtimes on customer-managed Kubernetes |
- | 4. Customer-Hosted Standalone: Mule runtime installed on bare-metal or private VMs |
- +-----------------------------------------------------------------------------------------+
Detailed 5-Dimension Deployment Comparison:
Deployment Model Infrastructure Manager Containerization & Isolation Load Balancing & Ingress Best Use Case
CloudHub 1.0 MuleSoft (AWS) Dedicated EC2 Worker VMs per app (0.1 to 16 vCores) Shared Load Balancer (SLB) or Dedicated Load Balancer (DLB) Standard cloud-first enterprise integrations with zero infrastructure management
CloudHub 2.0 MuleSoft (AWS / Hyperforce) Containerized replicas in Kubernetes (Shared or Private Spaces) Built-in Ingress Controller with automatic TLS edge termination Modern containerized cloud deployments requiring rapid autoscaling and granular vCores
Runtime Fabric (RTF) Customer / Cloud Provider Containerized Pods on customer-managed K8s (EKS, AKS, GKE, OpenShift) Ingress Controller (Envoy/Nginx) configured inside Kubernetes Organizations requiring cloud control plane with strict on-prem/VPC payload boundaries
Customer-Hosted Standalone Customer IT Team Non-containerized JVM processes on customer bare-metal or VMs Customer-managed hardware/software load balancer (F5, NGINX) Legacy data centers, air-gapped environments, or existing on-prem VM pools
3. Core Platform Services Across the API Lifecycle +-----------------------------------------------------------------------------------------+
- | ANYPOINT PLATFORM CORE SERVICES |
- | |
- | [1. DESIGN] ---> Anypoint Design Center (API Designer & Studio) |
- | [2. SHARE] ---> Anypoint Exchange (Public & Private API Portals) |
- | [3. SECURE] ---> Anypoint API Manager (Policies, SLAs & API Autodiscovery) |
- | [4. DEPLOY] ---> Anypoint Runtime Manager (Workers, Scaling & Logs) |
- | [5. OPERATE] ---> Anypoint Monitoring & Visualizer (Telemetry & Topology) |
- | [6. GOVERN] ---> Anypoint Access Management (RBAC, Environments & Identity) |
- +-----------------------------------------------------------------------------------------+
- 1. Anypoint Design Center
API Designer: A browser-based RAML 1.0 and OAS 2.0/3.0 modeling environment featuring context-aware code completion, real-time syntax linting, and visual schema definition.
Mocking Service: Automatically generates live simulated HTTP endpoints from RAML/OAS examples, allowing API consumers to test and validate contracts before developers write implementation code.
Anypoint Studio / Code Builder: Professional development IDEs for building executable Mule applications with a graphical canvas and two-way synchronization to Mule XML configuration files.
2. Anypoint Exchange
Enterprise Marketplace: The central catalog for discovering, sharing, and consuming reusable integration assets across the organization.
Asset Types: REST APIs, SOAP APIs, RAML/OAS fragments (DataTypes, Traits, ResourceTypes), custom policies, Mule 4 connectors (Salesforce, Database, JMS, HTTP), and pre-built integration templates.
Interactive API Console: Automatically renders API documentation with an interactive "Try It" console linked to live or mocked endpoints, enabling friction-free developer onboarding.
3. Anypoint API Manager & API Autodiscovery
Governance Engine: Configures, secures, and monitors APIs using runtime policies without requiring code changes to the underlying Mule flow.
API Autodiscovery: The mechanism that establishes a bidirectional link between a deployed Mule application and its corresponding API instance in API Manager.
The Mule application declares an <api-gateway:autodiscovery> configuration referencing the apiId generated by API Manager.
At runtime, the Mule runtime's API Gateway component polls API Manager, downloads active security policies, and applies them dynamically to incoming HTTP listener requests.
Standard Policies:
Security: Client ID Enforcement, Basic Authentication, IP Allowlist / Blocklist, JWT Validation, OAuth 2.0 Token Enforcement.
Quality of Service: Rate Limiting (SLA-based or tierless), Spike Control, Rate Limiting - SLA based.
Transformation: Header Injection / Removal, JSON Threat Protection, XML Threat Protection.
4. Anypoint Runtime Manager (ARM)
Single-Pane Deployment Interface: Deploys, manages, stops, restarts, and scales Mule applications across CloudHub 1.0, CloudHub 2.0, Runtime Fabric, and on-premises standalone runtimes.
Operational Capabilities: Configures worker sizing (vCores and worker counts), manages environment-specific application properties, schedules cron polling jobs, sets up automated alert triggers (e.g., CPU > 80% or deployment failures), and streams runtime logs.
5. Anypoint Monitoring & Anypoint Visualizer
Anypoint Monitoring: Built-in telemetry service providing real-time dashboards for tracking API throughput, latency, 4xx/5xx error rates, JVM heap memory, and thread utilization, combined with a centralized log search engine.
Anypoint Visualizer: Dynamically constructs live, real-time architectural topology maps by analyzing metadata from active Mule runtimes. It automatically categorizes and visualizes dependencies across Experience, Process, and System APIs, revealing performance bottlenecks and fault propagation.
6. Anypoint Access Management
Multi-Tenancy & Hierarchy: Manages Master Organizations and child Business Groups to represent corporate business units.
Environments: Isolates runtime domains (e.g., Design, Development, Test, Sandbox, Production).
Role-Based Access Control (RBAC): Grants granular permissions to users, teams, and Connected Apps.
Identity Management: Federates user authentication with external Identity Providers (IdPs) using SAML 2.0 or OpenID Connect (e.g., Okta, Microsoft Entra ID / Azure AD, PingFederate).
4. Exam Watch: Core Platform Components & Governance
Important
API Autodiscovery Pairing To apply API Manager policies to a Mule application, the application must include an <api-gateway:autodiscovery> element configured with the correct apiId pointing to the main flow's HTTP Listener. If autodiscovery is misconfigured, the application runs but policies are not enforced.
Warning
Control Plane Data Isolation The Control Plane manages metadata, policies, and telemetry, but never processes or stores actual customer transactional business payloads. Runtimes process payloads entirely within the Runtime Plane.
Tip
Anypoint Visualizer vs. Monitoring Use Anypoint Visualizer when you need an architectural topology map showing dependencies and API-led layering. Use Anypoint Monitoring when you need quantitative metric dashboards, JVM health statistics, and log search.