MuleSoft 4 Fundamentals

 We need software that integrates multiple systems seamlessly.

API-led Connectivity :

API-led connectivity is a methodical way to connect data to applications through reusable and purposeful APIs. 

These APIs are developed to play a specific role, unlocking data from systems, composing data into processes, or delivering an experience.

Three Types of API's :

1.System APIs

2.Process APIs

3.Experience APIs

System APIs :

System APIs, these usually access the core systems of records and provide a means of isolating the user from the complexity of any changes to the underlying systems. 

Once built, many users can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects. 

Think of APIs to access a database, at least the common operations or APIs to ease the access of certain errorless resources.

Note : Encapsulate data systems into an API.

Process APIs :

These APIs interact with and shape the data within a single system or across systems, breaking down the data silos, 

and are created here without dependence on the source systems from which the data originates. 

They only call the system APIs, and, as well as they don't depend on the target channels for which the data is delivered. 

A given process API, you have to think of a transformation, the data coming, for example, from the database to a certain schema delivered by a 

certain web page. Regardless of the web page API and the database API, in the middle, the logic is the same.

Note : Aggregate and process the result of System APIs.

Experience APIs :

Experience APIs are how data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source rather than setting up separate point-to-point integrations from each channel. 

An experience API is usually created with API-first design principles where the API is designed for this specific user experience in mind.

Note : Expose the data for frontend

API Language :

There are many, but the main ones are Swagger, or you may hear Open API 3.0, and RAML v1. 

RAML is native to MuleSoft.

RAML is a YAML-style language to define an API. 

Main Changes from Mule 3 :

1.Migrating MEL to Dataweave 2.0

2.Added Design Center

3.Flow Designer

4.Exchange