Mule 4 Design API with RAML 1.0

What you'll learn
API Design with RAML 1.0
Create API Design using Anypoint Designer
Test using Mocking Service
Publish to Exchange
Use API Notebook
Requirements
Basic Knowledge of RESTful Concepts
Unrestricted internet access
Description
A use case based approach to understand the API Design.
In this course -
We will first look into UseCase
Identify Resources as per the UseCase
Define methods for these resources
Define Query Parameters for Request
Define Headers for Request and Response
Model Data using DataTypes
Use DataTypes to define Request and Response
Add Documentation in the API
Create ResourceTypes and Traits for handling repeatable patterns in API
Modularize our API using library
Test our API using Mocking Service (without any implementation)
Publish our API to Anypoint Exchange to share within Organization
Publish our API to Public Portal to share with External Users
Interact with API using API Notebook for interactive tutorial
Version our APIs, Change Versions and Deprecate Old Versions
Why we should Design API first? How is this important?
It helps to -
First decide what the API wants to accomplish
First Design API Contract/Interface
Get User Feedback before Implementation
Helps in systematic approach towards implementation
Reduces Painful Repetition during Implementation
Reuse Organization Assets
Provide Good User Experience
Offer Easily Consumable APIs
Who this course is for:
API designer, developer, or architect
MuleSoft Developers/Designers trying to learn API Design with RAML
MuleSoft Developers/Designers trying to learn how to use Anypoint Platform for designing APIs
S