API Led Connectivity with MuleSoft

1. [12th August, 2017]: API-Led Connectivity
[SÃO PAULO]

2. All contents © MuleSoft Inc.
Agenda
2
• Introductions
• Agenda
• API Led Connectivity
• Q & A
• What’s next
• Networking time

3. All contents © MuleSoft Inc.
Introductions
3
About the organizer
Anupam Gogoi
Integration Developer
Avenue Code
São Paulo, Brazil
Email: agogoi@avenuecode.com
A SHOW OF HANDS:
Who is new to this MeetUp?

4. All contents © MuleSoft Inc.
Agenda
4
• What we gonna have today ?
– API Led Connectivity
– Q & A
– Event Architecture - by Victor Souza
– Q & A
– File Upload in REST API by Thiago Santana
– Q & A
– Mule 4 and Anypoint 7 by Cristiano Piccin
– Q & A
– Wrap up
Agenda

5. All contents © MuleSoft Inc.
API Led Connectivity
5
• One basic question ?
- How many of you heard of API Led Connectivity ?
• So what it is basically ?
- It's a new Business Model.Today, in the age of APIs, an API is not just a technical
interface on top of a database. On the contrary, your API is your new business model. In
the past, APIs were just seen as tools for developers. But nowadays, their scope is not
limited to internal use; API makers are exposing their APIs for external users around the
globe. For example, Google Maps APIs use the Uber APIs to calculate fare and travel time
to destination.
API Led Connectivity

6. All contents © MuleSoft Inc.
API Led Connectivity - How it is different ?
6
P2P Integrations
P2P Integrations

7. All contents © MuleSoft Inc.
API Led Connectivity - How it is different ?
7
In the P2P approach, one business operation is connected to another operation by
direct connection. In an organization where a lot of applications need to be integrated,
it becomes a mess with the P2P approach. Here are the main drawbacks of this
approach:
● Hard to change.
● Maintainability.
● High operation risk.
● Time to market.
P2P Integrations

8. All contents © MuleSoft Inc.
API Led Connectivity - How it is different ?
8
E2E Integrations
E2E Integrations

9. All contents © MuleSoft Inc.
API Led Connectivity - How it is different ?
9
E2E Integrations

10. All contents © MuleSoft Inc.
API Led Connectivity - Pace Layers
10
Building Architecture
API-Led Connectivity is based on Pace Layers. Now what
is a Pace Layer ?
● The Building Structure: It is not going to change for at
least 100 years.
● The Exterior: The Skin or Exterior of the building can be
redone in every 20-25 years.
● The Interior: The interior plumbing, air conditioner ,
heating, ventilation, electrical wiring can be replaced or
updated in every 15 years.

11. All contents © MuleSoft Inc.
API Led Connectivity - API Layers
11
API Layers
APIs are based on three distinct layers:
1. Experience Layer
2. Process Layer
3. System Layer

12. All contents © MuleSoft Inc.
API Led Connectivity - System Layer
12
System Layer
● They can be defined for various domains of
an organization, for example, ERP, key
customer and billing systems, proprietary
databases, etc.
● These APIs will change more infrequently
and will be governed by Central IT given the
importance of the underlying systems.
● These APIs should be maintained privately
inside the enterprise because it they provide
access to many sensitive informations.

13. All contents © MuleSoft Inc.
API Led Connectivity - System Layer
13
System Layer Advantages
Advantage of System API
One can modify the System API logic without affecting the other APIs (Process and Experience). For
example, if a System API is using SAP and, in the future, SAP needs to be replaced with Salesforce, this
replacement can be done easily modifying only the System API without touching anything in Process
and Experience layers.

14. All contents © MuleSoft Inc.
API Led Connectivity - Process Layer
14
Process Layer
● Responsible for shaping the data by
orchestrating and choreographing various
data by calling multiple System APIs.The
orchestration involves the aggregating,
splitting, and routing of data.
● The main purpose of Process APIs is to
strictly encapsulate the business process
independent of the source systems (System
APIs) from which the data originates.
● The Process APIs should be held privately
inside the organization as per
recommendation and should not be exposed
for public use.

15. All contents © MuleSoft Inc.
API Led Connectivity - Process Layer
15
Process Layer Advantages
Advantages of Process API
● Process APIs allow you to define a common process which the organization can share. Rather than
Order Fulfillment being implemented multiple times across the organization, it is defined once and
published for all to utilize.
● Rapidly transform data formats for a partner or app.

16. All contents © MuleSoft Inc.
API Led Connectivity - Experience Layer
16
Experience Layer
● The business process data is consumed
across a broad range of clients/channels
with different formats. For example, our
Order Purchase API (Process Layer) has
exposed data in the JSON format, but we
have a client application that accepts only
XML format, or vice versa.
● Data can be reconfigured easily to meet the
needs of multiple audiences. Also, we can
remove the unnecessary methods and
expose only the necessary methods in
Experience APIs in a simple way.

17. All contents © MuleSoft Inc.
API Led Connectivity - Experience Layer
17
Experience Layer New Clients
A Situation
Let's assume that we have two new clients
Partner 1 and Partner 2 that communicate via
XML and CSV formats respectively.
Solution
Since the Process API is expecting JSON,
you’re simply creating an experience API for
each partner to handle to data transformation
between each partner.This also allows the API
owner to establish SLAs and apply policies on
a per partner basis.

18. All contents © MuleSoft Inc.
API Led Connectivity - Experience Layer
18
Experience Layer Advantages
Advantages of Experience API
● Experience APIs are simple. Basically, they involve only the transformation of data. So, to meet a
wide range of clients that accept data in diverse formats, the Experience APIs do this rapidly,
decreasing the time to market.
● Security Policies can be applied in the Experience APIs.
● And the best part is one can monetize the Experience APIs.

19. All contents © MuleSoft Inc.
API Led Connectivity - Advantages
19
Advantages
Research shows that the API-led connectivity approach makes the development process 3 times
faster.
Because,
● One does not need to reinvent the wheel, decreasing the time to market.
● As the reusable APIs are already tested, the use of them makes the new implementations
bug-free.
● The reduced development time reduces the integration costs by around 70% (as per the
statistics).

20. All contents © MuleSoft Inc.
API Led Connectivity - Next ?
20
Next ?

21. All contents © MuleSoft Inc.
API Led Connectivity - Example
21
Example - Order Fulfillment
Let's implement the Order Fulfillment example. Traditionally we would have opted for this monolithic
approach. (A hypothetical flow). Let's assume we are exposing our response in JSON format.

22. All contents © MuleSoft Inc.
API Led Connectivity - Problems
22
Problems with the Approach
Main problems with this approach:
● Reusability
● New Client
● Time To Market

23. All contents © MuleSoft Inc.
API Led Connectivity - Identify the Layers
23
Identify the Layers
● Identify the System Layers.
● Create API for them and expose them to be consumed and reused by others.

24. All contents © MuleSoft Inc.
API Led Connectivity - Add Process Layer
24
Add Process Layer
Call System APIs in the Process Layer

25. All contents © MuleSoft Inc.
API Led Connectivity - Add Experience Layer
25
Add Experience Layer
Call the Process APIs in Experience Layer

26. All contents © MuleSoft Inc.
API Led Connectivity - Anypoint Platform
26
Anypoint Platform

27. All contents © MuleSoft Inc.
API Led Connectivity - Q & A
27
Q & A