Anypoint Platform Development: Fundamentals (Course #dev-fundamentals)

Programme every line is something you do

8 modules · 25 topics · in course-flow order

1. Module 1

   API-Led Before Line One

   Objective. Locate every flow you are about to build inside Lumen's three-layer landscape before writing any code.

   • Trace one click-and-collect order across Experience → Process → System APIs, timing each hop against the p95 < 300 ms budget
   • Assign one responsibility per layer: Experience shapes channels, Process orchestrates, System wraps POS and inventory
   • Price the point-to-point anti-pattern: count consumers per interface and size the blast radius of one schema change
2. Module 2

   Events, Flows & Connectors

   Objective. Construct a running order-intake application in Anypoint Studio 7.x/Mule 4.x, assembled from flows and subflows you can demo end to end.

   • Configure an Anypoint Studio 7.x workspace and scaffold a Mule 4.x project with its Maven pom.xml
   • Compose Mule 4.x events across flows and subflows: payload, attributes, variables vs record variables, flow-ref chains
   • Wire connectors to systems: HTTP Listener bound to port 8081, Database connector over JDBC, File polling source
   • Version the project on Git from hour one: initial commit, feature branch per user story, reviewed PRs before merge
3. Module 3

   DataWeave 2.x Mapping Essentials

   Objective. Build typed DataWeave 2.x mappings that reshape Lumen order JSON into the ERP-ready flat record, driven by input/output metadata.

   • Write mappings typed by DataWeave 2.x metadata (input/output headers), with filter, partition and reduce over a 10 k-record feed
   • Exploit DataSense: load sample JSON/CSV files as input metadata and preview every transform before deploy
   • Factor recurring logic into functions and a custom .dwl module reused across flows
4. Module 4

   Design the RAML 1.0 Contract

   Objective. Model the availability API in RAML 1.0 in Design Center and derive runnable APIkit flows from the published spec.

   • Model resources, methods, resourceTypes, traits and examples of the stock API in RAML 1.0
   • Publish the spec to Anypoint Exchange and scaffold APIkit router plus handler flows in Studio
   • Run the Design Center loop: edit, spin up the mocking service, collect consumer feedback, version the spec
5. Module 5

   Spec-First with OAS 3.x

   Objective. Scaffold an implementation straight from an OAS 3.x document and arbitrate RAML vs OAS for each new Lumen API.

   • Import an OAS 3.x document and convert RAML 1.0 <-> OAS without losing examples or security schemes
   • Scaffold APIkit flows from OAS so each operation binds to its dedicated handler flow
   • Navigate the 2.0 vs 3.x deltas: requestBody/responses, components, servers, nullable types, callbacks
6. Module 6

   Errors, Logs & MUnit Green

   Objective. Harden the order API with a typed error-handling strategy and deliver a green MUnit suite at a target 80% coverage.

   • Architect error handling: on-error-continue vs on-error-propagate, custom raise-error types, global handler
   • Correlate requests with a correlation-ID variable and structured loggers readable in Runtime Manager
   • Cover every branch with MUnit: mock-when, spy-verify, assert-equals on happy paths and each error case
7. Module 7

   Ship It: CloudHub Deployments

   Objective. Package the application with Maven and operate its first CloudHub deployment with per-environment properties.

   • Package with Maven and deploy to a 1 vCore CloudHub worker, reading the vCore-hour cost impact
   • Externalize properties per environment with placeholders and encrypted secure properties
   • Verify the live deployment: smoke-test endpoints, watch Runtime Manager charts, roll back on regression
8. Module 8

   Capstone: Click-and-Collect End to End

   Objective. Ship the complete Lumen chain — contract, implementation, green MUnit suite, deployed API — inside the latency budget.

   • Design the RAML 1.0 order contract, validate it through the mocking service, then scaffold APIkit handler flows
   • Orchestrate over System stubs: typed errors, correlationId end to end, streamed mappings keeping heap flat
   • Gate the release: MUnit coverage ≥ 80% including error routes, CloudHub deploy, smoke test under the 300 ms p95 target

References & Official Documentation every claim above has a source

Module 1

• Anypoint Exchange OverviewMuleSoft Docs

Module 2

• Mule Event StructureMuleSoft Docs

Module 3

• DataWeave ScriptsMuleSoft Docs

Module 4

• Creating and Importing API SpecificationsMuleSoft Docs

Module 5

• OpenAPI Specification v3.1.0Specification

Module 6

• Error HandlersMuleSoft Docs

Module 7

• Deploying Apps to CloudHub 2.0MuleSoft Docs

Module 8

• MUnit OverviewMuleSoft Docs

More in Developer