MuleSoft from Start: A Beginner's Guide
10 live-streamed (and edited) sessions to get started with MuleSoft.
Last updated
10 live-streamed (and edited) sessions to get started with MuleSoft.
Last updated
All of these sessions were first live-streamed in my . I tried not to do a lot in advance so we could actually explore everything during the live streams. Then, I edited the hour-long videos to make them a bit shorter and more digestable and uploaded them to YouTube.
You can also check out the GitHub repository to see all the links to the content and to take a look at each session's code, notes, and explanations.
Based on the book MuleSoft for Salesforce Developers, we reviewed the relevant topics and created an appropriate outline for the upcoming sessions. More info .
We connected our Mule app from Runtime Manager to our API in API Manager to apply security policies using API Autodiscovery. We learned how to apply CI/CD pipelines to our local project and how to do them using GitHub Actions.
We created some MUnit tests for our Mule app's flows and ran them in Anypoint Studio to increase the MUnit coverage.
We went through an overview of the different MuleSoft products and how to get involved with the community. More info .
We explained the API basics and learned what is MuleSoft's API-led connectivity approach. More info .
We created the requirements for our Blog API and started designing our API Spec. Finish your homework before the next session! More info .
We tested the API Specification using the mocking service in Design Center and adjusted a few things we had to change. Then, we published the API Spec to Exchange. Finally, we created a new Mule project from the published asset. More info .
We created a new Mule project with the scaffolded flows from the published API specification and started our API implementation / development. More info .
We reviewed how to implement the articles logic, created a Postman collection with its local+dev environments, and learned how to debug our Mule application. More info .
We confirmed the API works locally, so we deployed it to CloudHub (located in Runtime Manager) to test it in the dev environment. More info .