Every business need to integrate the above three actors and their engagement to systems for the best possible outcome. How to do it and Best way to do it , An Introduction

1. ANYPOINT PLATFORM
MULESOFT
1
Harish Kumar Reach Me at https://www.youtube.com/c/RightCode

2. INTRODUCTION ABOUT ME
HARISH KUMAR
▸ Almost 12 years working experience in IT industry
▸ Mulesoft and TOGAF certified Architect
▸ Have successfully completed implementation of mulesoft
product in various big projects
▸ Amateur taekwando ITF red belt
▸ Loves to drink beer and eat sushi
2
Reach me at echarish@gmail.com

3. INTRODUCTION TO MULESOFT
https://www.mulesoft.com/why-mulesoft
1000+
Customers
4.4+ billion integration
transactions per month
175,000+
developers
development time for
products, services and apps
higher productivity for
app development teams
customer
satisfaction
3
MULESOFT

4. BUSINESS AND CUSTOMERS OF MULESOFT
MULESOFT GROWTH OVER THE YEARS
https://www.mulesoft.com/why-mulesoft
Over the years Mulesoft has
grown from humble open
source beginning to becoming
one of the fastest growing
enterprise companies in
history
4

5. WHAT WE ARE TRYING TO ACHIEVE IN BUSINESS
INTEGRATION FACTORS OF BUSINESS
Engage customers with various business channels like mobile , web etc.
Collaborate with partners via new channels.
Accelerate employee productivity with micro-apps
• Every business need to integrate the above three actors and
their engagement to systems for the best possible outcome
5

6. API-LED CONNECTIVITY : THE EVOLUTION OF SOA
THE PROBLEM SPACE
• Yet, the heavyweight, top-down implementation approaches previously noted are not a
fit for the agility that today’s digital transformation initiatives demand.
• Point-to-point application integration is brittle and expensive to maintain. Service-
oriented Architecture (SOA) approaches provide some instruction in theory, but have
been poorly implemented in practice.
• The principles of SOA are sound: well-defined services that are easily discoverable and
easily re-usable. In practice, however, these goals were rarely achieved.
6
• While connectivity demands have changed,
the central tenets of SOA have not, that is, the
distillation of software into services that are
well-defined, re-usable and discoverable
• This problem lends itself to a service oriented
approach in which application logic is broken
down into individual services, and then
reused across multiple channels.

7. API-LED CONNECTIVITY CALLS FOR A DISTINCT ‘CONNECTIVITY BUILDING
BLOCK’ THAT ENCAPSULATES THREE DISTINCT COMPONENTS
• Interface Presentation of data in a governed and secured form via an API
• Orchestration Application of logic to that data, such as transformation and
enrichment
• Connectivity Access to source data, whether from physical systems, or
from external services
7
THE BUILDING BLOCKS

8. THREE TIER API LAYER ARCHITECTURE
Experience APIs
(purposeful API’s for Apps and Web)
Process APIs
(orchestration, composable APIs, Microservices)
System APIs
(legacy modernization, connectivity to SaaS apps, web services & Restful APIs)
Central IT
LoB Dev/ IT
Apps Dev
Accountability &
Ownership
8

9. LAYERS AND THEIR FREQUENCY OF CHANGES
Each API-led connectivity layer provides context regarding function and ownership
Layer Ownership Frequency of Changes
System Layer Central IT 6-12 months
Process Layer Central IT and Line of Business IT 3-6 months
Experience Layer Line of Business IT and Application Dev
4-8 weeks; more frequently for
more mature companies

10. WHAT DOES IT MEAN?
▸ Each layer is independent of other
▸ Each API is independent of other
▸ Everything is based on plug and play (Adapter design)
methodology
▸ Advantage of vast connector library provided by mule to make
out of the box connection to external system can be used
▸ Out of box solutions of API design can be used
▸ Implementation of API governance and security is as simple as
click of “policies” apply in “API Manager”

11. WHAT DOES IT MEAN?
▸ SLA’s on API can be applied with single click
▸ Changes can be applied and deployed with zero
downtime
▸ Creation of HA and cluster in Mule is super simple using
Mule Management Console
▸ Moving from on-premises to cloud is super simple
▸ Exposure of on-premises API to external partners using
cloud is easy

12. WHY MULESOFT
★ 100+ out of the box
connectors for Cloud
platforms, SaaS, Social etc.
★ Hybrid solution of cloud and
on-premises, with VPN
connection between them.
★ GUI based development,
with quick drag and drop
★ Various protocol conversions
available out of the box
★ Container based or
Independent deployment of
runtime
★ Lightweight Java based
server with minimum learning
curve for developers

13. THE BUILDING BLOCK OF API-LED CONNECTIVITY
Powerful Mule
core
(policies,
orchestration,
transformation,
caching)
productized APIs
(design, build, test, manage)
ubiquitous
connectivity
(connect to any system
or data source)
API gateway
(Manage all services
the same way)
13

14. BENEFITS OF API-LED CONNECTIVITY
BUSINESS BENEFITS
•IT as a platform for the business: By exposing data assets as a services to a
broader audience, IT can start to become a platform that allows lines of business
to self-serve.
•Increase developer productivity through re-use: Realizing an API-led
connectivity approach is consistent with a service oriented approach whereby
logic is distilled to its constituent parts and re-used across different
applications. This prevents duplication of effort and allows developers to build
on each other’s efforts.
•More predictable change: By ensuring a modularization of integration logic,
and by ensuring a logical separation between modules, IT leaders are able to
better estimate and ensure delivery against changes to code. This architecture
negates the nightmare scenario of a small database field change having
significant downstream impact, and requiring extensive regression testing.

15. BENEFITS OF API-LED CONNECTIVITY
TECHNICAL BENEFITS
•Distributed and tailored approach: An API-led connectivity approach
recognizes that there is not a one-size-fits-all architecture. This allows
connectivity to be addressed in small pieces and for that capability to be
exposed through the API or Micro-service.
•Greater agility through loose coupling of systems: Within an organization’s IT
architecture, there are different levels of governance that are appropriate.
Separate API tiers allow a different level of governance and control to exist at
each layer, making possible simultaneous loose-tight coupling.
•Deeper operational visibility: Approaching connectivity holistically in this way
allows greater operational insight, that goes beyond whether an API or a
particular interface is working or not, but provides end-to-end insight from
receipt of the initial API request call to fulfillment of that request based on an
underlying database query. At each step, fine grained analysis is possible.

16. HOW MULESOFT SUPPORT YOU

17. Q&A
Harish Kumar