Module 1 of 7

Anypoint Platform Fundamentals

Get a solid foundation in the Anypoint Platform ecosystem — organisations, environments, the Mule Runtime, and how all the pieces fit together.

3 lessons~2 hours

What is Anypoint Platform?

Anypoint Platform is MuleSoft's unified integration platform covering API design, implementation, management, and monitoring.

Anypoint Platform is a cloud-native iPaaS that lets organisations design, build, deploy, and manage APIs and integrations. It combines a full API lifecycle with a powerful runtime engine (Mule Runtime) and a set of cloud services.

The platform is structured around three pillars: Anypoint Exchange (a reusable asset catalogue), Anypoint Design Center (RAML/OAS editor and flow designer), and Anypoint Runtime Manager (deployment and monitoring).

Understanding how these pillars connect is critical before you write your first flow — decisions made at design time cascade into your deployment and maintenance costs.

Sample Anypoint Platform environment hierarchyyaml

Organisation: Acme Corp
  ├── Business Group: Engineering
  │   ├── Environment: Development  (sandbox)
  │   ├── Environment: QA           (sandbox)
  │   └── Environment: Production   (production)
  └── Business Group: Finance
      └── Environment: Production   (production)

The Mule Runtime Engine

Mule Runtime is the lightweight Java-based engine that executes your integration flows.

The Mule Runtime is a stateful event-driven engine. It listens for events (HTTP requests, database changes, file arrivals, messages from a broker) and processes them through a series of processors organised into flows.

Runtimes can be deployed on CloudHub 2.0 (MuleSoft's managed cloud), on-premise servers, or in customer-managed Kubernetes clusters via Runtime Fabric.

Each runtime instance is independently scalable and can be patched without taking other runtimes offline — a key advantage for enterprise uptime requirements.

Minimal Mule application descriptor (mule-artifact.json)xml

{
  "minMuleVersion": "4.6.0",
  "name": "my-first-api",
  "configs": ["my-first-api.xml"],
  "classLoaderModelLoaderDescriptor": {
    "id": "mule",
    "attributes": {}
  }
}

Organisations, Business Groups & Environments

Anypoint Platform uses a hierarchical structure to manage access, assets, and deployments.

A root organisation contains one or more business groups. Business groups isolate teams, billing, and vCores. Each business group has its own set of environments.

Environments are typed as either Sandbox (for non-production work) or Production. This typing affects features like analytics retention and SLA policies.

Roles and permissions are assigned at the organisation or business group level. Always follow the principle of least privilege — developers should not have Production deployment rights by default.

Next module

API Design with RAML & OAS