Introduction to MuleSoft
First lesson of the MuleSoft Basic Course. Watch the video, then move on to the exercises to make it stick.
What you’ll see
Section titled “What you’ll see”- What problem MuleSoft solves inside an integration architecture.
- What Anypoint Platform is and which components make it up.
- How the Mule Runtime relates to what you design in Anypoint Studio.
- The API-led connectivity approach and its three layers.
Key concepts
Section titled “Key concepts”MuleSoft is an integration platform: it connects applications, data and devices that were never designed to talk to each other. Instead of writing a custom integration for every pair of systems, each capability is exposed as a reusable API.
Anypoint Platform is the set of tools around that:
| Component | What it’s for |
|---|---|
| Anypoint Studio | The IDE where you design integration flows |
| Mule Runtime | The engine that runs those flows |
| API Manager | Applies policies, security and traffic control over the APIs |
| Exchange | Repository of reusable APIs, connectors and assets |
| Design Center | API design (RAML / OAS) from the browser |
API-led connectivity organises APIs into three layers:
- System — direct access to the source systems (databases, SAP, Salesforce).
- Process — orchestrates and combines data from several system APIs.
- Experience — shapes that data for whichever channel consumes it (web, mobile, partners).
Practise what you saw
Section titled “Practise what you saw”Inside any Mule flow you’ll transform data with DataWeave. These exercises are a good place to start: