Note: This is a comprehensive deck providing SEs & SCAs with a number of pre-canned slides and templates across

a number of key architecture themes

MuleSoft Architecture
Template Deck
Version 1.2
May 2023

Dr Mark Cornforth
Strategic Client Architect
MuleSoft UKI
 Slide not for external use.

About This Deck

This presentation will help guide your architecture-based conversations with customer CIOs, CTOs,
Enterprise Architects, Solution Architects etc about MuleSoft's PoV across a number of key strategic themes
(e.g. architecture framework & governance, cloud transformation, ERP transformation etc).

Who is this deck for?

● Strategic Client Architects
● Client/Platform SEs
● Customer Success SAs (CSSAs)
● Advisory & Professional Services

Why was this deck created?

This content is designed to help you:
● Share MuleSoft’s technical understanding and strategic thought leadership on key IT architecture challenges/themes
● Leverage already tried and tested content which can be re-used as-is and/or adapted to support the customer context

How do I use this deck?

● Navigate to the Contents page to understand the material which has been included (note that the order of the sections has
been arranged to allow you to tell the customer a story).
● A number of slides have speaker notes included to support the narrative and promote customer discussions.
● Architecture PoV examples have been included and which can be adapted to support your customer conversations but
please DO NOT share these directly.
 Slide not for external use.

Feedback
If you have any internal/customer feedback on this presentation and/or would like to contribute to the evolution of its contents,
please reach out to me at [email protected].

Recency
This deck will be updated regularly, but always check corporate resources for the most recent materials.
Contents
1. Industry Trends and Patterns in Integration
2. Problem Statement, Challenges & Business Initiatives
3. What are Building Blocks?
4. Composable Enterprise
5. MuleSoft Overview
6. Architecture Framework & Governance
7. Target Architecture
12. API-Led & Examples by Use Case
8. Architecture Themes
13. Monitoring
a. Cloud Transformation
14. Hyper-automatomation
b. Data Insights
15. Connectors
c. API/Digital Marketplace
16. Why MuleSoft?
d. ERP Transformation
17. Miscellaneous
9. Example Architecture POVs
18. Key Resources
10. API/Integration Roadmap
19. API Jokes
11. Customer Data Platform (CDP)
20. Appendix
12. API
All contents Monetisation
© MuleSoft, LLC
INDUSTRY TRENDS AND PATTERNS
IN INTEGRATION
Industry Trends & Technical Enablers for Integration
MuleSoft continues to lead the industry while operating at the forefront of integration, automation & innovation

Legacy Cyber- Edge

Public/Hybrid Cloud iPaaS Composability IoT EDA GraphQL AI/ML Hyperautomation
Integration Security Computing

>
<
EDI Exchange / B2B API Query Robotic Process
IoT
Cloud Native Zero-Trust Security Integration Microservices Graphs Automation
> >

Batch Processing Data Integration

Async APIs
API Creation & Broadcast/Pub Sub (Data Mesh) Business Process
SaaS Integration Automation
Management

SFTP File Gateway

Connectors & Evented APIs / Industry Universal API

Orchestration &
Accelerators Messaging & Queues Event Bus Templates Management
Web Services Aggregation

15+ Years Past 5-15 Years Past 3 Years 2023

CUSTOMER PROBLEM STATEMENT,
CHALLENGES & BUSINESS INITIATIVES
 Problem Statement
[Customer] is a complex organisation with a number of challenges

Strategic
Outcomes

Lots of Data No Re-use

Teams Operate
Increased
Legacy Estate in Silos Challenges Efficiency &
provide a
Flexibility
barrier to…

Integration is Slow Speed of Speed &

Hard & Complex Delivery Agility

Multiple Parties
Enhanced
Cyber
Security

Many Point-to-
Point Interfaces
Limited Innovation
Governance &
Fragmented
Control Change is Difficult Processes
All contents © MuleSoft, LLC & Expensive
Current Approaches Limit Ability to Adapt

Teams operate in silos Complex business model Data lacks recognition

❏ Contratual, behavioural and ❏ Unclear and fragmented ❏ Data isn't seen as a strategic asset
technical silos accountabilities, governance and ❏ Limited visibility and awareness of
❏ No common view on the control mechanisms common data standards and practices
availability, quality and location ❏ Challenges for data curation and ❏ Fragmented enforcement of data
of data exploitation governance, controls & mgmt practices

Too slow to deliver Fragmented IT landscape Inability to evolve

❏ Inflexible architecture doesn’t ❏ Lots of duplication ❏ Highly politicised industry
support incremental change ❏ Silo’d implementations ❏ Unpredictable but continual change
❏ Limited engineering delivery ❏ Data isn't discoverable, ❏ Operating model is limited by
agility accessible and re-usable technology landscape

All contents © MuleSoft, LLC

Problem Statement Summary
3 Pillars of Problem Statements Value Drivers
Success

Single Customer View

No Re-use Integration & Data
People No SCV across the Speed
Limited documentation, Complexity due to p2p,
1 organisation with 2 3
visibility and re-use of duplicate services &
limited data sharing,
digital assets limiting difficult to unlock &
engagement &
delivery & innovation unify data
collaboration

Process Resilience

End-to-End Visibility
Pace of Change Complexity
No single pane of glass
Too slow and hard to Hybrid & multi-cloud
4 for APIs & integrations, 5 6
make changes, adapt estate, tangled & tightly
governance, security &
Technology to new requirements & coupled, legacy & Agility
operations across IT
innovate digital
estate

Business
Drivers
Engineering Customer Increase
Reduce
Scale & Experience & Pace of
Costs
Productivity Centricity Innovation
All contents © MuleSoft, LLC
Our Understanding of your organisation ……

Pressure to
Transform Pressure 1 Pressure 2 Pressure 3 Pressure n

EA Mission Statement from Enterprise Architecture

Mission

Interlock to theme from Interlock to theme from Interlock to theme from

Business business strategy business strategy business strategy
Strategy

Business &
IT Initiatives Initiative 1 Initiative 2 Initiative 3 Initiative n

All contents © MuleSoft, LLC

Environment Agency - Our Understanding

Pressure to Rapid Climate & UK economy net zero Skills Gap & Reduction of
Transform Brexit
Environmental Changes by 2050 91,000 Civil Servants

“We create better places for people, wildlife and the environment. We put the climate emergency at the heart of
EA everything we do and help society adapt to environmental challenges such as flooding, drought, sea level rise and
Mission coastal change. We improve and protect the quality of our air, land and water by tackling pollution…..though
environmental regulation”

EA 2025 EA 2025 EA 2025

A NATION RESILIENT TO CLIMATE CHANGE HEALTHY AIR, LAND AND WATER GREEN GROWTH & A SUSTAINABLE
Business FUTURE

Strategy - Climate resilience - Cleaner & healthier air

- Leader in climate investment - Improved water quality - Support green economy through
- Incident & support ready - Nature & land better protected & better regulation
enhanced - Cut waste crime & develop circular
economy
- Net Zero by 2030

Business &
Workforce, skills & Innovation, Technology & Delivery, evaluation &
IT Initiatives Sustainability
location Data collaboration

All contents © MuleSoft, LLC

EXAMPLE - needs to be tailored for customer
Major IT Programmes & Business Initiatives

Workforce, skills & location Innovation, technology & data Delivery, evaluation & collaboration Sustainability

FCERM - Flood &

Coastal Erosion Risk
Field Water Testing DSP3 - Data Services
Management Strategy Future Farming Env. Land Management
(Cliq replacement) Platform
Action Plan
2021 Cross Cross Cross Cross Cross
Depart Depart Depart Depart Depart
Program Program Program Program Program

EU Exit & goal of

Livestock Information
Countryside Programme Flood warning system Project UnITY becoming a digital &
Programme
data driven organisation
Cross Cross Cross Cross
Depart Depart Depart Depart
Program Program Program Program

ADMS - Application Grant Management

LAP - Legacy Application Streams
Development & System
Programme
Maintenance Support

All contents © MuleSoft, LLC

EXAMPLE - needs to be tailored for customer
EA Current State & Challenges - Our Understanding

Focus Areas Data Silos Sustainability Security

Struggle to access & Need to share & expose

Multiple data points & Multiple organisations,
Current correlate data data to multiple partners
legacy systems that are complex tech stack &
(particularly suppliers (internal & external) from
State +20 years old partners
data) cloud & legacy systems

Challenge to access & Manual effort to gather Expensive resources &

Expensive resources &
correlate data internally data from different partners maintaining
Problem partners duplicating work
& with other agencies, sources secured end points or
across group
partners & suppliers (e.g. spreadsheets etc) none at all (back doors)

Impact to major Risk with data leakage

Impact programmes of work as Impact to cost, time & adds risk to group as a whole and potential national
a data organisation security risk

Integration How do you bring all this together?

Strategy

All contents © MuleSoft, LLC

EXAMPLE - needs to be tailored for customer
Setting up a new channel has traditionally been quite
complicated

Cloud SaaS
Platforms Social
Customers/ Mobility &
Partners/Suppliers Devices
57%
Projects that
companies set out
to deliver and
couldn’t follow
with reuse vs.
through
custom code

SAP

Packaged Apps Custom Apps Databases

All contents © MuleSoft, LLC
A Common Project-Based Approach
An eCommerce project aiming to provide real-time order status and order history

Web App API

Order status Order history

Project Objective

Web app provides real-time order status and order

history Aggregated
customer data
• Order data in OMS
• Inventory data in SAP
• Customer data in SAP, Salesforce

Inventory Customer Order

All contents © MuleSoft, LLC
A Common Project-Based Approach
An eCommerce project aiming to provide real-time order status and order history

On Time And Within Budget

Web App API

Limited Opportunity For Reuse

Tight Coupling = Brittleness Order status Order history

Difficult To Govern Aggregated

customer data

Meets Business Requirements

Inventory Customer Order

All contents © MuleSoft, LLC
A Common Project-Based Approach
6 months later and a new mobile app is required …… but there's no re-use

Mobile App API Web App API

Order status Order history Order status Order history

Aggregated Aggregated
customer data customer data

Inventory Customer Order

All contents © MuleSoft, LLC
 REGIONAL
Mission: De-risk the delivery of your digital transformation & SERVICES
accelerate business outcomes regionally & globally
Cloud/Digital
+ Ecosystem
How: Create a composable IT architecture using MuleSoft's GLOBAL
SERVICES
proven platform, approach & operating model Composable
Architecture

Three critical Success Factors are required:

1 2 3

FEDERATED EMPOWERMENT UNIVERSAL DIGITAL BACKBONE FUTURE-PROOF ARCHITECTURE

CAPABILITIES + FOR INTEGRATION + BUILT FOR CHANGE

Allow federated teams to connect Enterprise integration platform Built-in visibility, security and
applications across your digital making legacy system data and governance supported with an
ecosystem via automation services easy to access and effective operating model to
capabilities, no/low code platform consume while offering flexibility innovate and rapidly respond to
and universal API management. and scalability to meet evolving business requirements and
requirements. opportunities.

All contents © MuleSoft, LLC

Update slide with customer specific win themes
The Need to Shift Mindset ……
Shifting the mindset to embrace change

Data built in silos Data managed as an enterprise asset

Think and build large systems Think and build composable / modular
Traditional Thinking

Future Thinking
"Don't fix what isn't broken" Everything is changeable

Change is an unknown risk Change is a known tool

Siloed thinking and innovation Common & re-usable building blocks

APIs are not first-class citizens API-centric and API-first approaches

Too much server management Cloud managed & severless

All contents © MuleSoft, LLC

WHAT ARE BUILDING BLOCKS?
 What is integration?
Integration is the ability to seamlessly connect devices, applications and data across an organisation,
whether they are located on-premise, on cloud, or hybrid (a combination of both).

Effective integration drives:

• Customer experiences & engagement through a 360° customer view, omnichannel, e-commerce & others
• New products and services that reach new audiences & allow us to respond to market threats & opportunities
• IT operational efficiency which underpins our ability to quickly meet growing demands

Store Web Mobile Agent

Data
Consumers
Key:
Interface used to
exchange data

Data
Providers

Legacy Cloud Database Events Partners Suppliers

What is a building block?

Request Response

Key Characteristics:
• Clear business purpose & benefit
Contract • Simple, easy to use & understand
• Managed, secured, controlled & governed
Reusable • Well-documented, reusable, discoverable & accessible
Logic • Standards-based to maximise interoperability
building
block • Fast & performant
Connectivity • Operationally resilient, monitored & supported
• Version controlled with lifecycle management

Data
Let's bring a building block to life

Web Mobile

Order
Order Request Response

Key Operations: Contract Building block handles the security,

Order API

• Create Order processing of the data, and provides

• Update Order Logic this to the OMS in the required format
• Cancel Order
Connectivity

Order Management
System (OMS)
What are an organisation's core building blocks?
Digital Customer &
Colleague
Experiences

Request Response
Integration Platform

Customer API Product API Promotion API Payment API Inventory API Tracking API

Plus Golden
Identity API Pricing API Order API Fraud API Shipment API Insights API more … APIs

Account API Installation

Stores API Insurance API Repair API API Collection API

Data Providers /
Producers
Legacy Cloud Database Events Partners Suppliers
COMPOSABLE ENTERPRISE
What is a Composable Enterprise?

Compose:
Why do it? "to be selected and assembled
to satisfy specific requirements"

Architecture (IT):
What benefit does "the art or practice of
it provide? designing and
constructing IT
systems"

All contents © MuleSoft, LLC

Vision of the Composable Enterprise

Business-as-a- Digital Rapid Agility &

platform ecosystems innovation evolvability

All contents © MuleSoft, LLC

Composability is the foundation
for successful business
transformation
“A composable enterprise is an organisation
that delivers business outcomes and adapts to
the pace of business change. It does this
through the assembly and combination of
packaged business capabilities (PBCs).”

All contents © MuleSoft, LLC

APIs are
building blocks
for composed applications

A foundation
Chat Bot API
of business
Login API
Mobile App API
capability building
blocks that
Money
Transfer
API
Service Cloud Einstein balances
innovation speed
Customer
Database
ForEx System and operational
Core Banking System
stability
Composability through heterogeneous building blocks

API
REST gateways

GraphQL Evented
APIs

RPA Micro
services
Future of Innovation: Composable, Connected, Automated
Flexibility and Control

Discover Design

Build Manage

Secure Monitor

Multiple Persona

Multiple Building Blocks

Multiple Platforms
Composability requires Outside-In Thinking
Composability enables agility, speed and innovation

All contents © MuleSoft, LLC 33

MuleSoft Enables a Composable Enterprise to Emerge
…. providing agility, speed and innovation

Fast and agile by design

Pluggable, reusable building blocks

Secure across endpoints

Built-in visibility and governance
at every node

Dramatically lower costs

Lower development costs through reuse
and self-service

All contents © MuleSoft, LLC

What is a building block?

Core capabilities in
Request Response Reusable Building Blocks

Support all interaction types, e.g. queries,

commands, events

Productised and designed for ease of

Contract consumption
Reusable
building
Logic Easily managed for security, scalability,
block
and performance
Connectivity
Discoverable and accessible through self-
service

Allow system wide control mechanisms e.g.

monitoring, traffic control etc

Data
All contents © MuleSoft, LLC
Driving a Composable Enterprise
Leveraging APIs and integration to drive end to end digital experiences

Enable Experiences and

Business
New Business Models

Consumption

Composable enterprise
Ops supporting new
Model experiences and IT
agility
Production

Seamlessly Connect
IT
Systems and Data

All contents © MuleSoft, LLC

Making the composable enterprise a reality
Combining our technology with a tried and tested operating model = maximise re-use, minimise complexity

Intelligent Application Network

Fabric Any on-premise or
Business capabilities cloud-based system
Experience Process System

RESEARC
H

BUY

TRACK

GET
SERVICE

GET
ACCOUNT

Reusable building blocks translate complex system functions into

All contents © MuleSoft, LLC composable business capabilities
Driving value with a new approach
Thousands of enterprises are realising faster time to value

Go faster
64%
increased Faster ramp-up and increased productivity of
productivity skilled internal resources

Become more agile

78% Accelerated development and delivery
faster time to
market speed of integrations and APIs

74% Innovate more efficiently

reduced Lower your costs for run/change,
maintenance security, and governance; lower
costs
your maintenance effort
All contents © MuleSoft, LLC Source: Omdia 38
Thrive in an unstable world by being hyper-agile
Companies that grow during a crisis do this

Crisis time Growth time

Pivot Optimise Sell Grow Leverage Acquire

IT Drives Business Agility

Sources:
McKinsey: Stronger for longer: How top performers thrive through downturns
All contents © MuleSoft, LLC BCG: How Comeback Kids Will Build the New Reality
 Three Pronged
Approach to Success 1. Proven Approach
Experience
layer

Proven API-led connectivity & methodology for

Composable Enterprise Vision Process
layer
building a composable enterprise by unlocking
All 3 pillars are required to build and System
layer
data (no matter where it resides), decoupling
manage a composable enterprise, services faster, and establishing an architecture
which is integral to our customers’ built for change
digital strategies

2. Unified Platform
3. People Enablement One platform instead of many
Devs and
Expertise and proven C4E Business Teams - only unified platform for
operating model based
Integration
integration, universal API
on enablement and Marketplace
Marketplace APIs management, automation, API
collaboration that drives Discoverable, ecosystems, hybrid
reusable assets

self-service, reuse & Automation Monitoring deployment, full SDLC &

innovation across business Security no code/low code dev
IT
& IT

All contents © MuleSoft, LLC

How to deliver your Digital Transformation faster
MuleSoft enables you to transform quicker, with less effort, and reduced risk.

Faster Transformation Increase ROI and agility Fast and Reliable

Become customer centric Leverage OOTB Choose a vendor with a

quicker by an average of accelerators and direct to proven track record that is
4x by using a best-in-class save 1000’s of days of part of the Salesforce
integration platform. effort. ecosystem.
MULESOFT OVERVIEW
(Please see the MuleSoft 101 Template deck for more information)
 Evolution of MuleSoft

7 years 5

1 4 2020
Community Manager, 7
2 3 2018 Customer 360 &
2006 Salesforce acquisition Composer
Created as an ESB Mule 4 + Studio 7 2022
2013 2015 Hyper automation
First hybrid iPaaS API-led connectivity (RPA + Composer +
6 API Led)

2021
Universal API Management
DataGraph (GraphQL)
All contents © MuleSoft, LLC
MuleSoft Platform
One platform for automation, integration and API management

Salesforce Customer 360

solutions & packages
Cloud and Industry Solutions

Edge-to-core security
Security

Resilient operations
Monitoring

Persona-based app suites

Integration API Management Composer RPA

Universal cataloging
& reuse Exchange

Versatile developments
Runtime Engine & Services Hyperforce

All contents © MuleSoft, LLC

 MuleSoft Anypoint Platform
One platform for integration and API management

Apply security
Anypoint Security
Ensure compliance

Anypoint Design Anypoint Management

Design and build Center Center Apply policies
Automated testing Monitor performance
Citizen integration Troubleshoot issues
Anypoint Exchange

Runtime enforcement
Central marketplace Runtime Engine
& Services
Implementation logic
Reuse assets
Connectivity
Discover best practice

All contents © MuleSoft, LLC

 MuleSoft
MuleSoft Anypoint
Anypoint Platform
Platform
One platform for all integration needs

Ad-hoc
Admin/Ops DevOps App devs Developers
integrators

Designed for
varying
skillsets
Management
Plane

Designed to
Runtime
Plane “Run
anywhere”
On-Premise Hybrid CloudHub

Public Cloud

All contents © MuleSoft, LLC

 MuleSoft Anypoint Platform
One platform for all integration needs Designed for
varying
skillsets
> Ad-hoc > >
>
REST
> integrators
Admin/Ops DevOps App devs Developers SOA
< P
> < <
APIs & >
Management
Service Bus Web Services SaaS Integration

> >

Batch
GraphQL

>

>
>
Public Cloud >
>
>
On-Premise Hybrid CloudHub

Message Queues
Microservices B2B / EDI File Transfer
/ Pub-Sub

Designed to
All contents © MuleSoft, LLC “Run
MuleSoft Anypoint Platform
One platform for APIs and integration

Anypoint Security
Metadata - for example:
● Logs
● Performance stats
Anypoint Platform Anypoint Design Anypoint Management ● API definitions
Control Plane Center Center ● API policies
● System health
● Runtime
configuration
Anypoint Exchange

Runtime data - for

example:
Anypoint Platform Runtime Engine
● Request data
& Services
Runtime Plane ● Response data
● HTTP headers

On-premises Hybrid Hosted by Public Cloud Service Providers

All contents © MuleSoft, LLC & private cloud MuleSoft

 Deployment Options
CloudHub Customer-Managed Runtimes Customer-Managed Platform
(Standalone or RTF) (Private Cloud Edition)

MuleSoft Hosted

Customer Hosted

● MuleSoft is a Cloud First company ● For customers with strict PII and CIIO ● For customers with strict PII and CIIO
Considerations ● Rapid innovation processing requirements processing AND metadata
● Security and compliance OOTB ● Runtimes hosted on-premises or in requirements (rare)
● EU Cloud for European customers private cloud ● Control plane and runtime plane hosted
● GovCloud for US government ● Runtime Fabric for low-touch runtime by the customer
agencies deployment and management ● Very high IT overhead
● No Services SOW required ● Slightly higher IT overhead on ● Innovation at lower cadence
● Very low IT overhead customers ● Services SOW required

All contents © MuleSoft, LLC

ARCHITECTURE FRAMEWORK &
GOVERNANCE
Enterprise Architecture is Analogous to Urban Planning
An illustrative example

• No common services - public transit, parks or • Common services – parks, schools, roads, electrical,
schools water, transit, etc. = integration, data, access control,
app dev stack.
• Inefficient, siloed, everyone out for themselves
• City Plan = Multi-Year Roadmap & Future State
• Additions are ad-hoc
• Standards/Rules/Process = Governance
• Slow, inefficient, frustrating, insecure
• Lower TCO and lower risk
All contents © MuleSoft, LLC
 Useful link: API Strategy Template
Artefact Anatomy for API Governance
Governing API-enabled business propositions while enforcing standards & compliance throughout the lifecycle
Defines the high-level vision and strategic outcomes setting the
API Strategy (incl API Principles) direction for the future of integration as well as principles and rules to be
More Abstract

promoted and adhered to by everyone to achieve the vision.

Digital Strategy Data Strategy
Security Strategy Complementing organisational strategies with data & integration
Cloud Strategy … plus others promoted as a key digital asset and cross-cutting concern.

Conceptual (Abstract)
Reference architectures and patterns defined at an various abstract,
Reference Architectures &
Logical logical and concrete levels in relation to supported communication
Integration Patterns styles between source and target applications.
Physical (Concrete)*

Integration Technology Selection

Guidance/flowchart to ensure the right API integration platform,
Integration Patterns
pattern, API technology and API security policy is selected for the
Decision Tree Matrices
REST vs GraphQL vs Event APIs right use case.

API Security …. plus others

API / Integration Standards Enterprise level standards/guidelines for API designs &
standards/guidelines for the physical design and implementation
More Concrete

Standards & Guidelines API / Integration Guidelines

of APIs on particular integration platform(s) (e.g. MuleSoft
Platform Standards & Guidelines Anypoint).

A map of API and data assets for users across the organisation to find
API Catalogue the data needed, associated policies and usage guidelines.
API Catalogue & Models Industry / Regulatory Data Models Data models adopted by the enterprise in relation to organising
elements of data and standardising how they relate to one another and
Enterprise Data Models to the properties of real-world entities.
All contents © MuleSoft, LLC
*Delivered by engineering teams with architectural input, support & oversight
Artefact Anatomy for Data Governance
Governing data-enabled business propositions while enforcing standards & compliance throughout the lifecycle
Defines the high-level vision and strategic outcomes setting the
Data Strategy (incl Data Principles) direction for the future of data as well as data principles and rules to be
promoted and adhered to by everyone to achieve the vision.
API & Integration Strategy
More Abstract

Digital Strategy Security Strategy

Complementing organisational strategies with data promoted as
Cloud Strategy a key digital asset and cross-cutting concern.

Other Strategies

Enterprise (Abstract)

Reference Architectures & Logical Data and integration design principles, patterns and technology
Patterns recommendations for programmes to adhere and comply with.

Physical (Concrete)
Rules around data, Background information Background information
Data Standards Background information from Data creation to archiving and deletion that the
Standards & Guidelines organisation must follow when undertaking data activities.

Data Guidelines Guidelines for data to ensure conformance to industry best practice.
More Concrete

A map of data assets for users across the organisation to find the data needed,
Data Catalogue associated policies and usage guidelines.

Data Catalogue & Models Industry / Regulatory Data Models Data models adopted by the enterprise in relation to organising elements of
data and standardising how they relate to one another and to the properties
of real-world entities.
Enterprise Data Models
All contents © MuleSoft, LLC
Logical Architecture

● Marketplace acts as the front-

door for asset discovery and
reuse while driving the self-serve
and innovation agenda

● Management/Control Plane
provides full management,
access control , monitoring and
visibility of all digital products and
services across the ecosystem

● Runtime Plane consists of

capabilities (accelerators,
connectors etc) and policy
enforcement controls for
integration and lifecycle
management

All contents © MuleSoft, LLC

Integration Patterns across a Hybrid/Multi-Cloud Estate
What are integration patterns?

1. A pattern is a re-usable solution to commonly occuring requirements within IT

2. Integration patterns are defined at various levels from abstract EA patterns to those which
define implementable solutions

More
Abstract
Conceptual / Enterprise Patterns defined at an abstract level in relation to supported
Integration Patterns communication channels between source and target systems.
Enterprise
Architecture
Defines the responsibilities not only for the integration service but also Concern
Logical Integration Patterns for the requesting and responding applications. This builds on the
abstract patterns and imposes architectural standards and constraints.

Defines concrete service patterns capable of being used to generate Engineering

Physical Implementation Patterns runtime services. The service patterns defines the structure and Concern
behaviour of the integration service.
More
Concrete

For a fully comprehensive customer-facing deck on integration patterns,

All contents © MuleSoft, LLC please see: Enterprise Integration Patterns.
Integration Patterns across a Hybrid/Multi-Cloud Estate
Why use integration patterns?

API Integration Patterns:

1. Allow the API Strategy to be realised in relation to leveraging and exploiting approved
integration technologies for API based data exchange
2. Ensure that APIs are exposed in a consistent and standardised manner and
in conformance with agreed methodology and industry standards
3. Leverage best practice to simplify the integration architecture while improving
support, efficiency & performance
4. Align with security strategies, policies & standards for data protection to ensure key
(e.g. customer, financial etc) data is kept safe while minimising risk
5. Improve the level of architectural compliance of solution designs & reduce the flow of
enquiries & architectural exception requests thorough governance
6. Accelerate solution design and delivery while embedding best practice & compliance

All contents © MuleSoft, LLC

Integration Patterns for all Use Cases
Enabling connectivity across your on-premise, cloud, and hybrid ecosystem

> >
REST <
>
>
<
>

API Creation & Integration

SaaS Integration Management Microservices EDI Exchange / B2B API Query Graphs

>
>
> > >
> SOAP

< >
>

Migration & Sync Web Services Service Bus Batch Processing Evented APIs

>
>
>
>
>
>
>

FTP/SFTP File Broadcast / Robotic Process

Messaging & Queues Aggregation
Gateway Pub Sub Automation
All contents © MuleSoft, LLC
Integration Patterns
Integration patterns typically to fall into the three core categories …

# Type of data exchange Description

1 Batch When you can wait for hours or days (or longer) for processing

2 Near real-time When speed is important, but you don’t necessarily need it immediately

3 Real-time When you need information processed immediately

MuleSoft can support all of these integration patterns ….

Pattern: Batch Integration

If data has strategic value across the

wider enterprise, it can be 'published' to a
topic on a queue for multiple data
Application can be configured to consumers to 'subscribe' to Alternatively data can be sent directly to
Data can either be written out to file read data from the source file,
the Data Consumer via API calls or a
directly from the source system or transform, filter, redact, enrich,
separate file can be created in a format
extracted via a batch ETL process secure etc the data as required
which is consumable

queue

File publish subscribe

read
(csv, XML etc)
API call(s)
Data Source / Data
Application
Provider Consumer(s)

ETL file
read
or
File
file transfer ETL
Scheduled or manual trigger (csv, XML etc)
for data extract

Data can be consumed directly by the Data

Consumer system(s) or inserted into
storage via a batch ETL process

Notes:
● Arrows represent the direction of data transfer
Pattern: Real-time Integration

request
(e.g. json over https)

Data Source / System Process Experience Data

Provider #1 API API API Consumer(s)
respons
e

Data Source / System

Provider #2 API

Process APIs:
Experience APIs:
● Domain-aligned core competencies &
● Provide a means to simplify the way data is
business capabilities
accessed by a specific channel acting as a
● Provide a means of aggregating &
optimisation layer for user experience
System APIs: orchestrating data distributed across
● Provide all information required by a specific
● Expose and provide consistent managed access to data in multiple systems for a specific business
channel in the required format
core systems, which are often not easily accessible. purpose
● Provide a means of insulating consumers from the complexity
or any changes to the underlying systems
● Anti-corruption layer for adapting underlying assets (data
sources, applications, 3rd party/cloud services)

Notes:
● All APIs are designed to be highly reusable to enable the delivery of a composable architecture, provide delivery agility and a compelling return on investment (RoI)
● Data streaming also available as a real-time integration option although not shown here
Pattern: Near Real-time Integration

Data can either be published to a queue Data Consumer(s) can read the data
directly from the source system or pushed directly from the queue via an application/
to/pulled from an application/API API
queue

Data Source / publish subscribe Data

Provider
Consumer(s)

push or pull Application / Application / API(s)

API API

Application can be configured to process Application can process (transform, filter,

(transform, filter, redact, enrich, secure redact, enrich, secure etc) the data before
etc) the data before publishing to a topic providing to the Data Consumer(s) via an
on a queue API call

Notes:
● Arrows represent the direction of data transfer
 Legend: Mandated
API Standards Overview
Recommended
Anatomy of API Standards and Guidelines

More
Abstract

API Standards Created by the Enterprise Architecture

team & applicable to all APIs defined
API Guidelines across the organisation
Aligned to …

Platform Standards
Defined, communicated and enforced
by the MuleSoft C4E team
Platform Guidelines
More
Concrete
Organisational Standards,
Schemes & Specifications
Plus more …

Industry Standards, Schemes ● All organisational defined APIs must conform to standards & should align to guidelines to
& Specifications ensure alignment & consistency with industry best practice
● How is compliance against these manually/automatically assessed & enforced?
● An exception process will also need to exist for instances of non-compliance
All contents © MuleSoft, LLC
What are API Standards & Guidelines?
Defining the elements of an organisation's API Standards & Guidelines documents …….

API Standards API Guidelines

URL Structure HTTP Methods API Security API-First Approach Model APIs as Digital 'Products'

Resource URLs HTTP Response Codes Managing the Product & API Lifecycle

State Documenting APIs Naming Conventions

API Specifications
Management

Best Practice for API Design Abstraction

Custom Headers Data Exchange Format

Versioning Caching Error Messages Exemplar API Designs

Case Studies
Poor API Designs
Change Management Warning Messages

Plus more … Plus more …

All contents © MuleSoft, LLC
Why are API Standards Important?
Reasons to define organisational API standards and ensure compliance…..

✓ Alignment to industry standards, schemes and specifications increases

interoperability between applications
✓ Reduces reputational risk as a result of inconsistent and/or poor quality APIs
✓ Avoids inconsistent security & potential risk exposure with unmanaged, insecure
or unprotected APIs
✓ Maximises the API Consumer experience
✓ Reduces design, build, testing and support costs
✓ Provides increased agility and faster time-to-market
✓ Avoids regulatory fines for instances of non-compliance

All contents © MuleSoft, LLC

Data & Integration Governance
Governing data & API-enabled business propositions while enforcing standards & checkpoints throughout the lifecycle

An effective operating model for data and integration is needed to provide evangelisation and governance
against the strategy

Continual feedback & reviews

Other Design Authorities

Input
Significant architecture
Data & Integration Architecture Review reviews, approvals &
Design Authority Board(s) escalations

Business & product

Business Design strategy reviews,
Authorities approvals & escalations

'What' of Governance 'How' of Governance

Outcomes: Responsibilities:
✓ Improved compliance ● Oversee the architectural direction and governance of all data and integration related
✓ Increased quality propositions across the enterprise
✓ Increased visibility ● Review, provide guidance and agree on an outcome for project architecture designs and
✓ Accelerated delivery architecture decision requests to support compliance against the strategy
✓ Improved efficiency & reduced cost
All contents © MuleSoft, LLC
TARGET ARCHITECTURE
(RETAIL/CPG, FINANCIAL SERVICES &
ENERGY & UTILITIES)
 North Star Principles

1
Target Architecture (Retail/CPG)
Channel-agnostic
Journeys built for cross-channel use, High-level representation of the future IT estate underpinning the digital strategy
allowing for native journeys as appropriate

2
Omni-channel
Cohesive and joined up customer
experience

3
Interoperable
Functionality exposed as APIs irrespective
of requirements to protect future value

4
Modular
Apps and services built and run using micro-
service architecture style by enduring teams

5
Web-scale
Designed for low latency, elastic scalability
and fault tolerance to prevent bottlenecks

6
Event-based
Data streamed instead of scheduled for
near real-time replication and onward use

7
Cloud-native
Apps and services built for cloud, utilising
containers and integrated tool-chain

8
Resilient
Operationally resilient by design to ensure
business continuity

9
Secure Digital strategy supports B2C and B2B channels across the enterprise due to the pervasiveness of its technology and
Security embedded in design and tool-chain
by default adoption of north star principles that positively impact the customer, colleague and ecosystem experience.
 North Star Principles

1
Target Architecture (Financial Services)
Channel-agnostic
Journeys built for cross-channel use, High-level representation of the future IT estate underpinning the digital strategy
allowing for native journeys as appropriate

2
Omni-channel
Cohesive and joined up customer
experience

3
Interoperable
Functionality exposed as APIs irrespective
of requirements to protect future value

4
Modular
Apps and services built and run using micro-
service architecture style by enduring teams

5
Web-scale
Designed for low latency, elastic scalability
and fault tolerance to prevent bottlenecks

6
Event-based
Data streamed instead of scheduled for
near real-time replication and onward use

7
Cloud-native
Apps and services built for cloud, utilising
containers and integrated tool-chain

8
Resilient
Operationally resilient by design to ensure
business continuity

9
Secure Digital strategy supports B2C and B2B channels across the enterprise due to the pervasiveness of its technology and
Security embedded in design and tool-chain
by default adoption of north star principles that positively impact the customer, colleague and ecosystem experience.
 North Star Principles

1
Target Architecture (Energy & Utilities)
Channel-agnostic
Journeys built for cross-channel use, High-level representation of the future IT estate underpinning the digital strategy
allowing for native journeys as appropriate

2
Omni-channel
Cohesive and joined up customer
experience

3
Interoperable
Functionality exposed as APIs irrespective
of requirements to protect future value

4
Composable
Apps and services built and run using micro-
service architecture style by enduring teams

5
Web-scale
Designed for low latency, elastic scalability
and fault tolerance to prevent bottlenecks

6
Event-based
Data streamed instead of scheduled for
near real-time replication and onward use

7
Cloud-native
Apps and services built for cloud, utilising
containers and integrated tool-chain

8
Resilient
Operationally resilient by design to ensure
business continuity

9
Secure Digital strategy supports all B2C and B2B channels across the enterprise due to the pervasiveness of its technology
Security embedded in design and tool-chain
by default and adoption of north star principles that positively impact the customer, colleague and ecosystem experience.
Core Integration Capabilities
… required to deliver (and maintain) the benefits of the target architecture

People

Integration Platform Process

Technology

Core Technical Capabilities required for APIs/Integrations:

1. Multiple integration patterns (APIs, events, pub/sub, B2B/EDI, files etc)

2. Management of integrations via a single control plane
3. Asset discovery & reuse via a single marketplace (internal and/or external)
Capabilities
4. Security (i.e. transport and message level security)
5. Traffic mediation & control (e.g. spike arrest, rate limiting, content based routing etc) supported by an
6. Transformation (to/from Industry and/or Enterprise Data Models) effective operating
7. Orchestration and aggregation of data distributed across multiple systems model to promote
8. Connectors (e.g. to Salesforce, SAP etc to accelerate delivery) reuse, self-service
9. Automated governance to enforce standards compliance throughout the lifecycle and composability
10.API Monitoring to ensure availability, response times and conformance to SLAs
11.Full visibility of e2e service chain to support RCA, reduce MTTR etc
12.Automation of human tasks and business processes (e.g. RPA)
Future State with MuleSoft
MuleSoft makes it easier to deliver change, unify data, unlock value & realise strategic objectives

Strategic
Outcomes
Highly Reusable
Unified Data
Digital Assets Collaborative
Legacy Exposed Teams
via Modern APIs Enabling … Lower TCO &
Higher ROI

MuleSoft empowers seamless, Fast Time-to-

connected digital experiences Market Speed &
Agility
Innovative
Partnerships

Innovation
Loosely Coupled
Composable
Full Governance Architecture
& Control Enhanced
Agile & Cost Connected Cyber
Effective Change Processes Security
CLOUD TRANSFORMATION
Cloud Migration Challenges

1 2 3 4

Lift and shift approach The business stagnates and Tightly coupled monolithic applications Two siloed estates emerge,
causes massive service can’t innovate as they wait for are twice as time consuming to migrate 'old' and 'new', which directly
disruption and doesn’t the cloud which could take 5-7 to the cloud and require more compute affects customer experience
deliver cloud objectives years resources

5 6 7 8 9

£
Legacy is not built to Gap between old and new is Maintenance costs and Existing integration approaches What is the exit strategy
work with cloud nor vast and bridging this gap technical debt continue are a bottleneck and focus on and how easy is it to move
digital scale poses significant challenges to balloon cloud or on-premise not both workloads between
platforms?

All contents © MuleSoft, LLC

Key Insights & Lessons Learnt
We have supported many customers with their cloud transformation/migration journey …
these architectural themes enabled success using the MuleSoft approach & methodology

1. Consider wider integration needs (e.g. sFTP/FTPS, messaging, EDI etc) in addition to APIs
2. Define, agree and publish a cloud workload treatment strategy for applications, data & integration
(i.e. IaaS, PaaS, SaaS etc)
3. Define coexistence strategy between cloud & on-premise as digital services are migrated/transformed
4. Avoid a short-term view of integration, treat cloud as 'greenfield' and ensure legacy issues do not contaminate
& add unnecessary complexity
5. Define a cloud reference architecture for a composable enterprise encompassing all domains (e.g. customer, payment, product etc)
& journeys (e.g. customer onboarding etc) against which all solutions will be governed
6. Define, agree & publish integration patterns for extra-cloud, intra-cloud & hybrid-cloud (inter-cloud) comms
7. Consider end-to-end security early to ensure alignment with a zero-trust security model
8. Define supported APIs types (REST, GraphQL & Event) for cloud-based use cases
9. Define & agree robust operating model for all technologies & supporting processes
10. Ensure outcomes, value and ROI are well-defined & articulated within business case
11. Adopt agile, automation-first and API-first approaches to delivery
12. Define strategy for ensuring highly available & resilient operations to ensure no disruption & regulatory compliance
13. Consider API portability to negate cloud-provider lock-in & provide for an exit strategy

All contents © MuleSoft, LLC

On-Premise vs IaaS vs PaaS vs SaaS
There are multiple cloud hosting options including IaaS, PaaS & SaaS

On-Premise IaaS PaaS SaaS

Legend:
Applications Applications Applications Applications
IaaS Infrastructure-as-a-Service Pay-as-you-go service where a third
Data Data Data Data party cloud provider provides
infrastructure services (e.g. storage,
Runtime Runtime Runtime Runtime virtualization etc), as needed through
the internet.
Middleware Middleware Middleware Middleware
PaaS Platform-as-a-Service Cloud-provider hosts the hardware
O/S O/S O/S O/S
and software on its own infrastructure
and delivers this platform to the user
as an integrated solution, solution
Virtualisation Virtualisation Virtualisation Virtualisation stack, or service through an internet
connection.
Servers Servers Servers Servers
SaaS Software-as-a-Service Most comprehensive form of cloud
Storage Storage Storage Storage computing services, where an entire
application that is managed by a
provider, via a web browser.
Networking Networking Networking Networking

Customer managed

Service Provider managed

All contents © MuleSoft, LLC

Transitioning away from legacy to a cloud-enabled enterprise
Enabling a composable architecture which is future-proof, loosely-coupled and change agile

Phase 1 - Phase 2 -
Today Abstract Rationalise
Tomorrow

“Make the most of existing investments,

not throw it away” Core Systems

COMPOSABLE
MONOLITH
ENTERPRISE
All contents © MuleSoft, LLC
 How do we help accelerate cloud transformation?

Current State Transition State 1 Transition State 2 North Star

Primarily Traditional Hybrid Cloud Scaling Public Cloud Scaling (Almost) Fully Cloud Enabled

TRADITIONAL TRADITIONAL TRADITIONAL TRADITIONAL

(PRIVATE CLOUD) PUBLIC CLOUD (PRIVATE CLOUD) PUBLIC CLOUD (PRIVATE CLOUD) PUBLIC CLOUD (PRIVATE CLOUD) PUBLIC CLOUD

IBS components IBS components IBS components IBS components

Non-IBS components Non-IBS components Non-IBS components Non-IBS components

● Secure & control traffic to legacy ● API-led connectivity adopted to create the foundation for a composable enterprise ● Line of business teams able to create
MuleSoft Capabilities

applications (e.g. mainframe to ● New cloud based Digital Products created with no bridging logic simplifying the digital experiences with core assets
optimise MIPS usage & costs) implementation managed & governed by IT
● Expose legacy APIs as modern ● Anti-corruption layer hides complexity, data translation & connectivity concerns ● API Marketplace empowering internal
RESTful endpoints abstracting between cloud & on-premise & external discovery, reuse and
complexity while being portable to innovation through a unified end-user
● Center for Enablement (C4E) established to support and empower autonomous teams
public cloud experience
to quickly build and deploy new services

● On-premise integrations become ● Accelerated delivery by 3-5x across entire API life-cycle allowing faster migration to ● Future platform fully responsive to
Outcomes

cloud-ready and portable while cloud providing cost savings through switching off legacy business, regulatory, market demands
ensuring continuity of service ● Self-service & asset reuse allowing applications to be built faster accelerating time-to- and opportunities
value while improving resilience and negating cloud-provider lock-in
● Enhanced customer & employee experiences with reduced TCO & reduced risk

Unified platform enabling a fully composable enterprise across hybrid & multi-cloud
All contents © MuleSoft, LLC
Legend: IBS = Important Business Service
Approach to Cloud Migration
UK Financial Conduct Authority (FCA) define an Important Business Service (IBS) as:

“a service provided by a firm to one or more clients of the firm which, if disrupted, could
(1) cause intolerable levels of harm to any one or more of the firm’s clients; or
(2) pose a risk to the soundness, stability or resilience of the financial system or the orderly operation of the financial markets”

Current State Transition State 1 Transition State 2 North Star

Primarily Traditional Hybrid Cloud Scaling Public Cloud Scaling (Almost) Fully Cloud Enabled

TRADITIONAL TRADITIONAL TRADITIONAL TRADITIONAL

(PRIVATE CLOUD) PUBLIC CLOUD (PRIVATE CLOUD) PUBLIC CLOUD (PRIVATE CLOUD) PUBLIC CLOUD (PRIVATE CLOUD) PUBLIC CLOUD

IBS
IBS components IBS components IBS
components IBS components

Non-IBS components Non-IBS components Non-IBS components

Non-IBS components

● IBS and Non-IBS components ● IBS components remain on- ● Selected IBS components targeted ● IBS components split across traditional
hosted on-premise premise for public cloud and public cloud
● Non-IBS components targeted for ● Non-IBS components split across ● Non-IBS components fully hosted on
public cloud traditional and public cloud public cloud

If delivered with the right technologies, people and processes, this approach enables ……

Increased speed & agility, faster time-to-market, reduced costs, resilient operations & a future-proof foundation
All contents © MuleSoft, LLC
Approach to Cloud Migration
State Description Mulesoft Capabilities Outcomes

● Private cloud optimised (where possible) to reduce run ● Anypoint deployed on-premise to secure & ● On-premise integrations
and change costs while enabling delivery control traffic to legacy applications (e.g. become cloud-ready while
● Foundations for public cloud platform established to mainframe to optimise MIPS usage & costs) ensuring continuity of service
provide speed, agility and elastic scalability ● Expose legacy APIs as modern RESTful endpoints
Current State abstracting complexity of underlying
Primarily Traditional technologies while being portable to public cloud

● Best of breed technologies leveraged on public cloud for ● Anypoint deployed to public cloud to ● Accelerated delivery across
selected use cases offering improved digital experience complement & co-exist with cloud-native services entire API life-cycle unlocking
● Private and public clouds interoperate ● New cloud based APIs designed & built with no the full potential of APIs and
● Approach helps achieve scale while mitigating risk and bridging logic simplifying the implementation accelerating time-to-value
proving key technologies ● MuleSoft approach to API-led connectivity ● Self-service and asset reuse
Transition State 1
● Operating model established for non-critical workloads adopted to create a composable enterprise, allowing applications to be
Hybrid Cloud Scaling unlocking value opportunities & reducing the built faster
burden of integration to digital transformation ● Enhanced customer and
● Mulesoft leveraged as an anti-corruption layer employee experiences
● Operating costs reduce as vendors take responsibility hiding complexity, data translation & connectivity delivered with reduced TCO
for greater elements of solution concerns between cloud & on-premise
● Robust operating model to ensure key services are ● Center for Enablement (C4E) established to
managed & controlled within overall risk appetite support and empower autonomous teams to
● Public cloud services become more critical as public cloud quickly build and deploy new services
Transition State 2 use cases scale
Public Cloud Scaling

● PaaS / SaaS solutions accelerate speed to market and ● MuleSoft Composer leveraged allowing line of ● Future platform fully
increase proportion of resources increasing customer business teams to create digital experiences with responsive to business,
value core assets managed & governed by IT market demands and
● Risk reduced by building experience within multiple cloud ● API Community Manager (ACM) leveraged to opportunities
platforms create an API Marketplace empowering external
North Star ● Majority of key applications, data and integrations innovation through partners & third-parties
(Almost) migrated to public cloud offering range of connected
Fully Cloud Enabled digital experiences
All contents © MuleSoft, LLC
 Cloud Migration Treatment Strategies
Three treatment strategies are available to support the migration to public cloud with each offering
varying degrees of change, risk and cost

# Name Description Considerations

1 Re-host Also referred to as 'lift-and-shift', Approach can provide some infrastructure/ hosting cost savings and
where the application running on improve resilience but the code-base and any technical debt and/or
premise, e.g. on bare-metal, is re- support issues with the legacy application are not resolved and are
Legacy Modernisation

IaaS hosted onto an IaaS provision on transitioned to cloud.

public cloud.

2 Re-platform Approach extends the 're-host' Approach can provide cost savings, improved resilience and
approach and allows the application reduced risk with the opportunity to resolve technical debt and/or
to be updated (e.g. to the latest support issues with the application, but not fundamentally change
IaaS version) to bring back into support the core architecture or underlying solution.
and adopt new capabilities/
features.

3 Re-architect Approach is usually part of a wider Approach allows for the delivery of business outcomes through
Transformation

business transformation initiative composability treating cloud as 'greenfield'. This requires a re-
Business

PaaS allowing for the broader adoption of architecture / re-design of the solution with a focus on key principles,
cloud technologies (PaaS & SaaS) e.g. cloud-first, interconnectivity, re-use, speed/agility, flexibility,
SaaS to be fully leveraged & exploited. connected digital experiences etc. Benefits include reduced TCO,
reduced risk, faster time-to-market and increased innovation.

All contents © MuleSoft, LLC

Cloud Migration Strategy
Options for delivering against the cloud adoption & migration strategy

Migration from on- Migration from IaaS to

premise to Public Cloud cloud-native SaaS/PaaS
IaaS technologies

1a Public Cloud v1 1b Public Cloud v2

On-premise
(IaaS) (PaaS & SaaS)

Approach: 'Re-host' & 're-platform' 'Re-architect' Cloud

migration strategy (lift- migration strategy technologies
and-shift) ..plus other
as part of wider fully leveraged
with minor change SaaS
business & exploited
(e.g. to bring products transformation CloudHub (AWS)
into support)

Benefits: 1. Reduced Cost 1. Business outcomes through composability &

2. Improved Resilience connected digital experiences
3. Reduced Risk 2. Interconnected, future-proof and flexible
architecture
3. Reduced TCO
4. Reduced risk
5. Speed & agility
All contents © MuleSoft, LLC
6. Innovation
 Integration Patterns
Reference Architecture: API-Led Connectivity 1 New cloud based APIs on GCP (UC1 & UC2)

Legend: 2 Anti-corruption layer (UC1)

API-led connectivity is key to
creating a composable = Mule API 3 Traffic mediation on-premise (UC1)
enterprise, unlocking value Channel App #1 Channel App #2 Channel App #3
opportunities and reducing the
burden of integration to digital
transformation. MuleSoft Anypoint Platform can
compliment and co-exist with Legacy Apps
MuleSoft Anypoint Runtime native cloud offerings while
Plane can run anywhere. providing support for REST,
Each API is individually GraphQL & Event/Async APIs
managed, secured and made
available for discovery & re- Firewall
use through the Anypoint
Control Plane. Cloud Load Balancer + WAF Controls
DMZ / Security Tier Legacy API
Gateway
Internal API Consumer
Application(s)
Experience API #1 Experience API #2 Experience API #3 MuleSoft Anypoint can run
on-premise to mediate &
Anti-corruption layer hides read/ control traffic to legacy
Experience Layer Legacy APIs mainframe to ensure MIPS
write complexity, data translation &
connectivity concerns between usage is prioritised &
cloud & on-premise. optimised for key API
Consumers. Anypoint can
Process API #1 Process API #2 Process API #3 also expose SOAP APIs as
modern RESTful endpoints.
3
1 Process Layer
2

Legacy Systems

Anti-Corruption
System API #1 System API #2 System API #3 System API #4 System API #5 System API #6

networking
bandwidth
Layer

& resilient
High
Identity Customer Fraud Payment Risk Product
SoR SoE
System Layer

Event Backbone Evented (Async) APIs provide event-driven

notifications, messages & data exchange

Public Cloud Platform (e.g. GCP, Azure, AWS) Traditional On-premise

All contents © MuleSoft, LLC
 Reference Arch. for Reference Data
Exchange Rate Interest Rate
Provider(s) Provider(s) Legend:

Mobile App Third-Parties Regulated TPPs = Mule API

External Reference Data

(Financial Services)
Firewall

Cloud Load Balancer + WAF Controls

DMZ / Security Tier
Internal API
Consumer
Application(s)
Ref Data API Open Data API Exchange Rate API Interest Rate API

Experience Layer

Mule API listens for

Reference data made changes to core reference
available to internal & Reference Data Process API data and publishes this to
external API Consumers a queue and 'Ref Data'
via System & Experience

resilient networking
topic

High bandwidth &

APIs with caching Process Layer

Ref. Data API Product API Account API

Master Data Management
(MDM)
Reference Data Product Account
Reference Data
Management (RDM)
System Layer

Cloud based consumers Event Backbone

'subscribe' to 'Ref Data'
topic to pick up latest
changes to reference data Public Cloud Platform (e.g. GCP, Azure, AWS) Traditional On-premise
All contents © MuleSoft, LLC
API Testing Framework MuleSoft Anypoint Platform provides
the ability to create functional tests which
can be configured and triggered to
CloudHub (AWS)

for App Migration ensure no regression of the e2e service

chain
MuleSoft API Test Control
Legend:
Automation / API Monitor Plane
Streamlining the testing approach while & Visualiser
= Mule API
insulating apps from the movement of others
External API Test Automation Suite
(e.g. Postman, SOAP UI)

MuleSoft API Monitor & Visualiser

Secure private allows all migrated / updated APIs to
Firewall be individually monitored with full
connection
visibility of the e2e service chain.
Cloud Load Balancer + WAF Controls
DMZ / Security Tier

Legacy API
Experience API
Consumer App(s)
Experience Layer

n1 Routing API Mule API handles the routing &

tio security with communicating with
Process API Op the migrated API while insulating
legacy API Consumers from
Process Layer on 2
Opti Party API change
(legacy)
r API
rovide
d API P
MuleSoft Anypoint Platform provides Party API Migrate Customer Legacy
the ability to create unit tests as part of (migrated) Application
an automated build process

bandwidth &

networking
resilient
Customer

High
System Layer
SoR SoE

Event Backbone

All contents © MuleSoft, LLC Public Cloud Platform (e.g. GCP, Azure, AWS) Traditional On-premise
 Legend:
API Security Across Clouds & IdPs: Approach 1 = Mule API

Let's consider an example where:

- A Customer API has been migrated from on-premise to public cloud
- A legacy API Consumer application on-premise requires access to this API
- Changes can be made to the legacy API Consumer app
- Different IdPs and CAs are leveraged across clouds
- An end-to-end zero-trust security model must be adopted

Public Cloud Platform (e.g. GCP, Azure, AWS) Traditional On- (Private Cloud)

CA2 client cert 2

CA2 server CA2 client cert 1
ClientId2 / Secret2 cert
ClientId1 / Secret1

Public-Cloud API mTLS

2 Consumer Application(s)
Party API Legacy API
(migrated) Consumer App 1

Firewall

Firewall
High bandwidth &

networking
resilient
IdP2 (Cloud) IdP1 (On-premise)
System Customer
CA2 (Cloud) Layer CA1 (On-premise)

Once mTLS connection established, Mule API Legacy API Consumer app requires
enforces security policies (e.g ClientId/ some changes (e.g. URL, security
Secret, OAuth etc) calling out to CRLs, JWKS context) to consume migrated API on public
etc services to ensure e2e security. cloud.
All contents © MuleSoft, LLC
 Legend:
API Security Across Clouds & IdPs: Approach 2 = Mule API

Let's consider an example where:

- A Customer API has been migrated from on-premise to public cloud
Option for Routing API to be deployed to public cloud to
- A legacy API Consumer application on-premise requires access to this API minimise network security impact and change on-premise.

- Changes cannot be made to the legacy API Consumer app Architecture decision required with options assessed
based on respective pros and cons.
- Different IdPs and CAs are leveraged across clouds
- An end-to-end zero-trust security model must be adopted
No changes required
to API Consumer app
Public Cloud Platform (e.g. GCP, Azure, AWS) Traditional On- (Private Cloud)

CA2 client cert 2

CA2 server CA2 client cert 1
CA1 client cert 1
ClientId2 / Secret2 cert
ClientId1 /Secret1
Legacy credentials

Public-Cloud API mTLS

2 Consumer Application(s) Legacy API

Load Balancer
Party API Routing API 1
Consumer App

Firewall

Firewall
High bandwidth &

networking
resilient
IdP2 (Cloud) System Customer IdP1 (On-premise)
Layer
CA2 (Cloud)
CA1 (On-premise)

Mule API enforces security policies (e.g Mule API insulates API migration from legacy API
ClientId/Secret, OAuth etc) calling out to Consumer by providing protocol, URL security context, Load Balancer updated to
CRLs, JWKS etc services to ensure e2e data etc transformations while offering controlled canary route all traffic to Mule API for
security. releases and routing rules between legacy & cloud. routing decisioning logic.
All contents © MuleSoft, LLC
 Legend:

Supporting East-West API Comms = Mule API

Let's consider two examples where:

1. Microservices need to communicate intra-domain (within a given domain)
2. Microservices need to communicate inter-domain (across domains)
while enforcing end-to-end security and access control.

1 2

API Consumer API Consumer

App App

Firewall

Firewall Firewall
Party API

Party API Ref. Data API

Party Product Party Prefs API
Holdings API

Customer Dat
a
Dat
a Mule APIs are independently managed, Reference Data
System Customer secured, resilient, scalable, change System
Layer agile, monitored and governed. Layer

Intra and inter-domain communication

are fully supported (in addition to extra-
domain communication).
Public Cloud Platform Public Cloud Platform
All contents © MuleSoft,(e.g.
LLCGCP, Azure, AWS) (e.g. GCP, Azure, AWS)
Providing API Portability across a Hybrid/Multi-Cloud Strategy
Designing for cloud hosting migration & providing for an exit strategy

Design principles which are key to designing solutions for portability:

1. Leverage open standards including security

2. Favour microservices
Illustrative
3. Leverage containers
4. Adopt loose coupling through architectural layering
5. Leverage technologies which run on any cloud
6. Agree approach to data consistency

MuleSoft Anypoint platform differentiates itself through:

● Ability to run anywhere

● Proven approach to API-led connectivity
● Unified platform for full integration & API lifecycle
● Embedded API implementation layer
● API monitoring & visualisation
● Universal API Management

Benefits:

● Provides agility & flexibility

● Prevents cloud-provider lock-in
● Achieves scale while reducing risk
● Enables collaboration through asset discovery & re-use
● Reduces proliferation of integration technologies
● Allows API governance through a single control plane
All contents © MuleSoft, LLC
DATA INSIGHTS
(please see MuleSoft Data Strategy deck for more)
 Roadblocks get in the way of Digital Transformation
… and not only cause significant business problems but also stifle innovation

● Organisations face a number of

people, process and technology
challenges that get in the way of
digital transformation.
● Data silos are one of the critical
roadblocks to improved customer
experiences and innovation.

Source: MuleSoft
All contents 2023LLC
© MuleSoft, Connectivity benchmark report
 Data silos are a persistent brake on innovation
… and are causing significant business problems for most enterprises

ORGANISATIONS WITH
CHALLENGES CAUSED BY DATA
SILOS
10% ORGANISATIONS WITHOUT
CHALLENGES CAUSED BY DATA
SILOS

90% ● Integration requirements are increasing

across the enterprise.
● Data silos remain a roadblock to improved
performance and customer experience.
● 90% of enterprises cite data silos as a core
challenge to realising their business
objectives.

Source: MuleSoft
All contents 2023LLC
© MuleSoft, Connectivity benchmark report
 Multiple Causes for Data Integration Failure
Organisations face a multitude of different data integration challenges

Unlocking the power of enterprise data is a complex initiative that requires a

future-proofed strategy supported by the right integration platform.

Source: MuleSoft
All contents 2023
© MuleSoft, LLCConnectivity benchmark report
 Harnessing the power of data is complex

SAP

976 90%
of technology
applications in the
average enterprise, leaders struggle
with only one- with data silos
quarter connected*

39
systems in an
average business
transaction

All contents © MuleSoft, LLC 93

Source: MuleSoft 2022 Connectivity benchmark report
Current state of data and analytics

Format, Massage,
Get Data Put It in a Lake Look at the Report What's Next?
Maintain & Govern It

● Organisations struggle to connect to all the systems they have, but the seem to find new and interesting ways of filling data
lakes, warehouses and various cloud data stores.
● Governance and information management become diminishers of information trust and reporting silos emerge.
● Delivering sustainable and timely business action is limited to MI & reporting.
● Limited consideration given to getting the right data to the right place at the right time to provide actionable insights.

All contents © MuleSoft, LLC

Data Value Economies of Scale...
...and the danger of diseconomies

Value of Data Data Data

Data “Economies of “Returns to “Diseconomies
Scale” Scale” of Scale”

Number of Data Sets

All contents © MuleSoft, LLC
The Need to Shift Right ……
Shifting the mindset to embrace change

Data built in silos Data managed as an enterprise asset

Think and build large systems Think and build composable / modular
Traditional Thinking

Future Thinking
"Don't fix what isn't broken" Everything is changeable

Change is an unknown risk Change is a known tool

Siloed thinking and innovation Common & re-usable building blocks

96

APIs are not first-class citizens API-centric and API-first approaches

Too much server management Cloud managed & severless

All contents © MuleSoft, LLC

The Composable Business Enables Data Flow

DIGITAL DIGITAL DIGITAL

Analyse & Act
Application Networks comprise Access data stores and
Digital Products which model transactional systems
your channels, processes, and
data.
DIGITAL DIGITAL DIGITAL
These reusable building blocks
translate complex system
functions into composable
business capabilities.

How they interact with each

DIGITAL DIGITAL DIGITAL DIGITAL other adds an extra 97
dimension
of data: your organisation’s
behaviour.
Unlock
Flow business data
in real time

All contents © MuleSoft, LLC

An Agile Data Strategy Requires Five Shifts

From Monolithic Data Projects ...to Rapid Incremental Value

Data Focused Outcomes Driven

Complete Data Curated Sets

Reactive Insights Proactive Sensing

Linear Processes Cycles of Learning

Decisions Mostly “Top-Down” Decisions Mostly at “Front Lines”

Data is a cost Data has value

All contents © MuleSoft, LLC

Agile Data Sprints are Organised Around Data Consumers
Clearly defined business
value and executive
stakeholders
Data consumers and key
business processes
Company Vision Business identified
and Value Prop Strategies
Connected Insights Data and Insights
Why do your How are you planning and Experiences Consumers
Data Acquisition and
customers do to execute on the
business with you? vision you identified, Integration
and evolve faster than For each strategy: Are data consumers internal
Why are you seeking your competition? or external (partners,
Is all the required data available
to transform your What connected customers, regulators etc.)?
for analysis?
business? Strategy #1: experiences do you
How do you deliver on need to be able to Who will consume the data
Are there any privacy or data
your mission? provide? and insights? (sp. Job roles,
residency restrictions around use
How do you measure # of individuals)
of the data?
value to your What specific business
stakeholders? questions do your Where do they work? (Web /
Is data of the right granularity,
stakeholders need to Mobile / In App)
quality and currency?
Strategy #2: ... answer in order to be
able to execute on this? What key business
How frequently is data refreshed?
workflows are they
How up-to-date does data have to
responsible for?
be to support the business
question?

Who is involved in preparing the

data for analysis?
All contents © MuleSoft, LLC
Key Principles for Data Products
Required to deliver against the strategy, enable composability and achieve business outcomes

DATA INTEGRATION

1
Data must have accountability and 7 Avoid a short-term view of integration
ownership

2 8
Leverage open standards (including
Standardise data across the enterprise
security)

Exploit data at the most effective and Adopt loose-coupling, favour microservices
3 9
relevant point in the value chain & leverage containers

Secure data at creation, curation, when APIs must be designed following an API-
4 10
handling, storing and transmitting First approach and built for reuse
100
5
Curate data, ensuring it is assured, 11
APIs must be secured following a defence
discoverable and interoperable in depth strategy

6
Endure data as an asset beyond individual
12 Abstract APIs from underlying implementation
projects

All contents © MuleSoft, LLC

High-Level Logical Architecture
Data democratisation and decision-making through connected data exchanges

Smart
Data
Mobile Tablet Web IoT Suppliers Partners Consumers
Devices

Data
consumption Federated Data Platform
Integrated data platform

MuleSoft Anypoint (iPaaS)

ET
L
Application network &
integration platform
Data Lake,
Analytics & Data Lake & Visualisation
Business Cloud data storage, analysis &
Insights business intelligence platform

Data ingestion Data

& acquisition decisions Note: Scenarios where data sources integrate directly
into the data lake include bulk data load, ETL, mass file
transfer/streaming (10’s GB, TB etc) etc

Data Sources /
Providers
Legacy Events Data Hubs / SaaS Files
Applications Warehouses Applications
All contents © MuleSoft, LLC
Vision: Joined-up experiences and empowerment for customers

Digital Marketplace

Application Network & Integration Platform

Fully Governed Application Access
APIs and Connected Apps & Devices
Data Security, Tokenisation and Access Control Events
Integrations Marketplace & Custom Connectors Reusable Integration Assets
Management and Monitoring of Integrations Actions From User Input and System Events Private
Universities Partners
Health
Data Hospitals /
Data Acquisition authorized re- DataAPIs
APIs Agencies
Suppliers
live scoring
Legacy Systems identification
Continuous and Transform Privacy
Scheduled data Engineering Data Science
collection and Canonical
Anonymisation Classification, insights to action embedded
translation. Models & live scoring data views
Pseudonymisatio Predictions, and
Relationships
Events
n Recommendation
Reconciliation
Clean & prepare Tokenization s
Train and deploy Granular, De-
Harmonize
models identified, Data & Insights Portal
Resolve identities Privacy by design Feature engineering Harmonized and
across sources and by default and scoring Augmented
SaaS Query Federation
Applications Content Governance and Data Trust
self- Data Asset Discovery and
serviceexpl
oration
Recommendations
Raw Integration
Self-Service Data Exploration
Trust-Level
Longitudinal Augmented Analytics
Records Open-Standards Access
operationalize Dashboards and Data Storytelling
Elastic Scale for Compute and Capacity ICS, Regional and National insights
Business-level
Data Asset Availability and Resiliency Data Platforms / Lakes Aggregates Data Alerts and Collaboration
Data Catalog and Ontology
Existing ETL Enterprise Data Catalog Lineage and Quality
Tooling and Batch Data Classification and Governance metadata
Legacy Data Hubs, Data Acquisition
Warehouses,
Flat Files Security and IAM
Cloud Platform Services Monitoring and Alerting

Sources Consumers
Vision: Joined-up experiences and empowerment for customers

Digital Marketplace

Application Network & Integration Platform

Fully Governed Application Access
APIs and Connected Apps & Devices
Data Security, Tokenisation and Access Control Events
Integrations Marketplace & Custom Connectors Reusable Integration Assets
Management and Monitoring of Integrations Actions From User Input and System Events Private
Universities Partners
Health
Data Hospitals /
Data Acquisition authorized re- DataAPIs
APIs Agencies
Suppliers
live scoring
Legacy Systems identification
Continuous and Transform Privacy
Scheduled data Engineering Data Science
collection and Canonical
Anonymisation Classification, insights to action embedded
translation. Models & live scoring data views
Pseudonymisatio Predictions, and
Relationships
Events
n Recommendation
Reconciliation
Clean & prepare Tokenization s Data & Insights Portal
Train and deploy Granular, De- Analytics that People Love to Use
Harmonize
models identified,
Resolve identities Privacy by design Feature engineering Harmonized and Query Federation - Live and Extract
across sources and by default and scoring Augmented Content Governance and Data Trust
SaaS
Applications Data Asset Discovery & Recommendations
self-
serviceexpl
oration
Raw Integration

Trust-Level
Longitudinal Self-Service Data Exploration
Records operationalize Augmented Analytics
Open-Standards Access
Elastic Scale for Compute and Capacity ICS, Regional and National insights Dashboards and Data Storytelling
Business-level
Data Asset Availability and Resiliency Data Platforms / Lakes Aggregates

Data Catalog and Ontology

Existing ETL Enterprise Data Catalog Lineage and Quality
Tooling and Batch Data Classification and Governance metadata
Legacy Data Hubs, Data Acquisition
Warehouses,
Flat Files Security and IAM
Cloud Platform Services Data Alerts and Collaboration
Monitoring and Alerting

Sources Consumers
MDM Integration
Target architecture & integration approach for MDM through pub-sub (preferred) &
request-response/batch file transfer patterns to provide choice & flexibility
Option 1 Publish-Subscribe Pattern
Mule App either (1) listens for changes to
core master data or (2) MDM calls Mule Option 2 API Request-Response Pattern
App with core master data, which
publishes data to a queue and master data Option 3 Batch File Transfer Pattern
topic
External Data
Sources Reusable Building Block

Master Data
Event Backbone Consumers (or the consumers’ system
Management (MDM)
APIs) subscribe to the required
Option 1 master data topics
Provider

Internal Data
Sources

New Consumer Applications

Mule Apps can retrieve data from Mule API locally caches Option 2 Consumer(s)
internal and/or external data sources data to prevent repeated
and cleanse, transform, enrich etc requests to the core MDM
the data before providing to MDM platform.
Consumers can make a Mule API call (on-demand or on a scheduled basis)
to retrieve the latest set of master data through defined access controls

Mule App extracts data from the

MDM platform on a scheduled/adhoc Option 3 Legacy Consumer Applications
basis to file & provides to legacy
consumers Consumer(s)
All contents © MuleSoft, LLC
API/DIGITAL MARKETPLACE
 What make a Product Successful?

✓ It’s actually useful! (API does the job) ✓ It’s easy to use (API Documentation)
✓ It’s Reliable (Infra, HA, NFRs) ✓ It’s Maintained/Warranty (operations team, API contract)

But one thing is crucial…..

Marketing, Discoverability & Try-before-you-buy (API Ecosystem/Portal)

Vs. API
API

API
API

All contents © MuleSoft, LLC

 API 'Storefronts' are not all about
building external ecosystems

All contents © MuleSoft, LLC

API/Digital Marketplace Enabling the creation of seamless digital experiences
through a connected application network
Facilitating the discovery, promotion and re-use of
Unlock Digital Assets Agile App Development
digital assets through a unified end-user experience
● APIs ● Reusable Integration Assets
● Events ● Fully Governed & Secured
● RPA Bots Application Access
● Connectors ● Take Action From User Input and
● API Specifications System Events
● API Fragments
● Sample Code
Public Partners Suppliers Internal Staff …. plus more
● Mock Services

Identity & Access Management

Support Ticket Management

External Marketplace Internal Marketplace
Public API Registries
API/Digital Marketplace
E-Mail & SMS Providers

Billing/Charging/Payment
Asset Publication

Separation of concerns between

IT
internal & external actors enabled
Estate
Data Legacy Events Data Hubs / Cloud through visibility & access controls
Platforms Applications Warehouses Applications

All contents © MuleSoft, LLC

 CORE BENEFITS
API/Digital Marketplace ✓ All digital assets unlocked (APIs, API fragments, events,
Facilitating the discovery and re-use of digital assets across connectors, RPA bots, sample code etc)
the IT estate through a unified end-user experience ✓ Digital assets managed, governed, promoted & marketed
✓ Self-service provides opportunities for collaboration & innovation
✓ Accelerated time-to-market for new propositions through re-use
✓ Facility for APIs to be tested prior to onboarding & adoption
✓ Consistent branding with streamlined & unified end-user
experience
✓ Operating model provides cost efficiencies through automation
Public Partners Suppliers Internal Staff

Identity & Access Management

Support Ticket Management

External Marketplace Internal Marketplace Public API Registries
API/Digital Marketplace
E-Mail & SMS Providers

Billing/Charging/Payment

Asset Publication

Cloud Cloud Cloud Cloud Mule SaaS

Legacy Data Hubs /
Apps Data Apps Data Apps Applications Separation of concerns between internal & external
Apps Warehouses
actors enabled through visibility & access controls
All contents © MuleSoft, LLC CloudHub On-premise
MuleSoft’s product offerings are uniquely positioned to
deliver against the API/Digital Marketplace Vision

Vision for API/Digital Marketplace

Anypoint Exchange
Consolidate all APIs into a single place

Create
API Community Manager
vibrant API
Build and engage your API communities
ecosystems

H1, ‘23

API Experience Hub

Build developer portals in minutes

All contents © MuleSoft, LLC

Anypoint Exchange
Create a consolidated source of truth for all enterprise APIs

Consolidate APIs built anywhere

Automatically discover APIs and relevant documentation from
any environment using CI/CD pipelines

Package your APIs into products

Describe your APIs with asset information, interactive
documentation and simulated behavior

Streamline API consumer onboarding

Empower developers to discover, explore and get started
with your own APIs, assets and best practices

Jumpstart development and governance

Use hundreds of templates, APIs and governance rules from
the MuleSoft ecosystem

All contents © MuleSoft, LLC

API Community Manager
Let's take a look ….
Global Bank External Portal

All contents © MuleSoft, LLC

API Community Manager
Let's take a look ….
Embracing Our Own Technology

All contents © MuleSoft, LLC

Maximising API value needs a shift in mindset
Making APIs discoverable and consumable is imperative in digital ecosystems

Consolidated API view

Where do I catalog all APIs I want

to publish to consumers?
I want a single source of truth.

Publish APIs to consumers 55%

consumers cite lack of
Do we have expertise to build and maintain portals? good documentation as
I want to save time and resources. an obstacle to adoption*

Sarah Consumer support

* Postman - State of APIs
API Product Our users want support from product and community.
Manager I want build and engage ecosystems.

All contents © MuleSoft, LLC

Drive API adoption by growing a vibrant community
Marketplaces and portals play complementary roles
Manage your communities
to drive innovation
Make each project faster
with reuse

Jumpstart development

Siloed Systems

Drive API adoption

Next gen developer experiences
Asset reusability
Standardised best practices
API based architecture API Community Manager /
Accessible customer data Experience Hub
Disparate data sources
Inaccessible digital assets
Exchange

All contents © MuleSoft, LLC API Programme Maturity

Consumer Journey

● What is this? ● Will this meet ● How do I ● How do I ● What’s coming

my needs? make this scale? next?
● Is this useful work?
to me? ● Can I trust this ● Are we ● Can I provide
API provider? ● How do I get meeting SLAs? feedback? Can
● How does this help? we co-create?
help me solve ● How easy is it to ● How do we test
my problem? get started? ● Does the API when changes ● What are the
offer a good are made? future plans for
DX? this API?
All contents © MuleSoft, LLC
Great Developer Portal Framework

Understanding First Touch Establishing

API Reference Support
Provider & API Experience Trust
● Business case ● Self service Minimum Viable ● FAQ ● Navigation that
● Use cases signup/ ● Includes all resources ● Bug Report points to answers
● Case studies registration ● Description of each ● Contact support ● Calls to Action
● App gallery ● API key resource ● Blog ● API Status
● Biz models/pricing provisioning ● Complete resource ● Off-site channels ● Changelog
● Terms of Service ● Getting Started URLs (Twitter, YouTube) ● Roadmap
guides ● Complete cURL call ● Analytics ● Blog
● Tutorials ● Header ● Forums ● Forums
● SDKs ● Description of ● Live support
● Code Samples parameters (Discord/Slack)
● Sandbox ● API status/error codes

Extended
● Single page (fully
searchable)
● Copy code functionality
● Personalized reference
● Version navigation
● Downloadable API
description file
● Interactive reference

All contents © MuleSoft, LLC

What Do the Best Portals Have in Common?

1. Business case is stated

2. First Touch Experience

3. API reference is industry leading

All contents © MuleSoft, LLC

Anatomy of a good Digital Product Marketplace

● As a marketplace owner:
○ Easily create multiple profiled portals
○ Moderate User Registration and provide profile based visibility
○ Publish existing APIs to the portal and control visibility of its instances
○ Maintain API governance
○ View API utilisation and Portal metrics
● As a marketplace consumer:
○ Search and view APIs, documentation and business use cases
○ Request access to API instances
○ First Touch Experience: Test API in API console within the marketplace
○ View API lifecycle state and roadmap

All contents © MuleSoft, LLC

Example API/Digital Marketplaces

● Salesforce
● Standard Bank
● HCSC (Health Care Service Corporation)
● Vopak

Please see this ACM Portal Repository link and Quip link for an up to date list of
customer portals (some of which are referenceable)

All contents © MuleSoft, LLC

ERP TRANSFORMATION
Target Architecture: ERP Migration
Exploring the target architecture and integration approach for ERP consolidation & migration

Phase 1 - Phase 2 -
Today Abstract Rationalise
Tomorrow

COMPOSABLE
MONOLITH
ENTERPRISE
All contents © MuleSoft, LLC
Build a modern, microservices-based business

Monolith Microservices

OMS CRM APIs

Custom
code
FI AM

HR MM
Le
ga
ER cy
P
PM CO

All contents © MuleSoft, LLC

The migration approach ….
3
Migrate data on-demand for
SIT and UAT

Configure S/4HANA
2
Validate business 4
requirements Migrate data to production
with mocked APIs using existing tools

1 Define APIs to unlock 5

business functions Run ERPs in parallel
as microservices
Phased cutover

All contents © MuleSoft, LLC

Step 1: Define APIs to unlock business functions

App App App Standardize requirements,

1 2 n data structures, and data
policies with APIs for each
De-risk
program ERP module

S/4HANA Versioning allows tracking

Legacy ERP APIs
instances and managing changes

AM FI HR HR FI AM ERP module owners control

HR FI AM Accelerate
delivery
API sign off, acceptance,

Dev
PM QM PP PM QM PP changes, and data loads

Test
PM QM PP
MM SD CO MM SD CO
MM SD CO
Populate APIs with sample
data to define data reqs
Accelerate
delivery
RDBMS Migration
HANA
(Oracle, DB2) dataset
All contents © MuleSoft, LLC
Steps 2 & 3: Validate business reqs, migrate data for testing

App App App Mocking service enables

1 2 n parallel development and
testing prior to data
Accelerate
delivery migration

S/4HANA
Legacy ERP APIs
instances Connect apps to validate and
AM FI HR HR FI AM test early in the project
De-risk
HR FI AM program

Dev
PM QM PP PM QM PP

Test
PM QM PP
MM SD CO MM SD CO
MM SD CO
Load ERP modules with test
data using APIs
Accelerate
delivery
RDBMS Migration
HANA
(Oracle, DB2) dataset
All contents © MuleSoft, LLC
Steps 4 & 5: Phased migration to production,
cutover to S/4HANA

App App App

1 2 n Flexible migration to
production
Business
outcomes

S/4HANA
Legacy ERP APIs
instances Monitor program
AM FI HR HR FI AM performance in real-time
De-risk
program

Prod
PM QM PP PM QM PP

MM SD CO MM SD CO

RDBMS Migration
HANA
(Oracle, DB2) dataset
All contents © MuleSoft, LLC
Benefits of MuleSoft’s API-led migration approach

● Avoid “big bang” migration

De-risk your
program ● Connect apps to validate and test early in the
project

Accelerate ● Design, develop, test, and deploy in parallel

delivery ● Leverage OOTB S/4HANA configuration

Reduce ● Cycle through UAT and training faster

API-led spend ● Rationalize systems
migration

Maximise
● Microservices architecture for future reqs
business
outcomes ● Migrate by module, geo, LOB, etc

All contents © MuleSoft, LLC

CUSTOMER DATA PLATFORM (CDP)
 Architecture Overview: Customer Data Platform

Data
decisions &
actionable
insights
SALES SERVICE MARKETING COMMERCE COMMUNITY ANALYTICS

DIGITAL HQ CUSTOMER DATA PLATFORM (CDP)

Digital Asset
Management (DAM)

Content Management
INTEGRATION System (CMS)

Data ingestion
& acquisition
Customer systems
outside of the
Legacy SaaS Master Data Enterprise Resource Order Management Data Data Salesforce
Application(s) Application(s) Management (MDM) Planning (ERP) (OMS) Warehouse(s) Lake(s) ecosystem

Data
consumption
& actionable
insights

LEGEND: OOTB Connector/Interface Customer/External/Third-Party Application Flow of Data

All contents © MuleSoft, LLC
API MONETISATION
What do we mean by API Monetisation
The process of driving revenue to enterprises via api channels

1) Offering access to APIs in 3) Exposing Data, Services and Capabilities for

exchange for revenue customers to build on top of

2) Defining Usage Plans, Pricing Models

and Ser vice agreements
All contents © MuleSoft, LLC
 API Monetisation is NOT adding credit card payment to
APIs
Nobody signs a $1,000,000 deal on their corporate Amex

Product Definition Order Taking Provisioning Fulfillment Billing Cash

Aligning on a formal Capturing a specific Distributing access Completion of the Compiling and sending Collecting billed
set of bundled offerings agreement between keys that connect a request/response a bill that revenue from
with pricing and SLA a customer and a customer order with process for production is derived from a customers and tracking
models attached to provider so both can a set of assets and calls between a customer order it within enterprise
them so customers can agree on how the deploying any policies consumer and a and production cash tools
place an order for relationship will work and assets necessary provider usage along with
something specific and how payment will for governed fulfillment adjustments based on
be made SLA or other criteria

All contents © MuleSoft, LLC 133

 API Monetisation is NOT adding credit card payment to
APIs
Nobody signs a $1,000,000 deal on their corporate Amex

Product Definition Order Taking Provisioning Fulfillment Billing Cash

Aligning on a formal Capturing a specific Distributing access Completion of the Compiling and sending Collecting billed
set of bundled offerings agreement between a keys that connect a request/response a bill that is derived revenue from
Optimizing these processes is key to making an API product business “operable” with
with pricing and SLA
models attached to
customer and a
provider so both can
customer order with a
set of assets and
process for production
calls between a
from a customer order
and production usage
customers and tracking
it within enterprise
few errors and a labor model that isn’t linearly coupled to customer growth.
them so customers can
place an order for
agree on how the
relationship will work
deploying any policies
and assets necessary
consumer and a
provider
along with adjustments
based on SLA or other
cash tools

something specific and how payment will for governed fulfillment criteria
be made

All contents © MuleSoft, LLC 134

 Direct monetisation starts before
customer deals are closed
Metering & monetizing APIs is enabled across several touch points of the Order-to-
Cash process:

Product Definition Order Taking Provisioning Fulfillment Billing Cash

In the Product Definition phase, In the Fulfillment phase, providers:

providers:
● Meter requests via policies
● Set a rate plan
In the Billing phase, providers:
● Define a bundle and SLAs
● Use the agreed to payment terms to
In the Order Taking phase, consumers:
process and transform the metering
● Agree to payment terms associated output into a bill
with a bundle

All contents © MuleSoft, LLC

 To take advantage of monetisation opportunities,
it’s recommended that enterprises mature across 5 foundational
capabilities

Figure 1: 5 key capabilities for monetisation. Each with 3 evolutionary practices. APIs Figure 2: MIT Study shows top monetizers have
built on MuleSoft play key roles in at least 7 practices much more advanced capabilities vs bottom ones

Comparison of capabilities. How much more mature those

classed as “top performers” are in each capability vs “low
Key performers”
Practices.
Companies evolve
data monetization
capabilities, with
more advanced 1
practices building
on foundational
predecessors

3
2
Capabilities

2 4
3
Primary role
Enabling role
4
1 5

Sources:
MIT - https://cisr.mit.edu/publication/2019_1101_DataMonCapsPersist_WixomFarrell
All contents © MuleSoft, LLC
MuleSoft Mobilize consulting
API-LED & EXAMPLES BY USE CASE
API-Led Connectivity (ALC)
Maximise re-use, minimise complexity

API Consumer

● Provide a means to simplify the way data is accessed by a specific Developers

channel acting as a optimisation layer for user experience Discover, self-
Experience ● Provide all information required by a specific channel in the required serve, reuse, and
layer format consume
● Composition: aggregation of process APIs and/or system APIs

● Domain-aligned core competencies & business capabilities LOB IT

● Provide a means of aggregating & orchestrating data distributed Discover, reuse
Process across multiple systems for a specific business purpose assets, and
layer ● Composition: orchestration of System APIs & other Process APIs compose data

Experience
layer ● Expose and provide consistent managed access to data in core Central IT
systems, which are often not easily accessible.
System ● Provide a means of insulating consumers from the complexity or any Unlock assets
layer changes to the underlying systems and decentralize
● Anti-corruption layer for adapting underlying assets (data sources, access
applications, 3rd party/cloud services)
● Composition: indirectly called using the process layer via
API Provider composition, or triggered events

All contents © MuleSoft, LLC

 MuleSoft customers build less, manage less, spend less
Value of leveraging MuleSoft's unique API-led approach

By leveraging an API-led approach, MuleSoft customers are able to maximise reusability and limit total development demand. This
saves huge amounts of cost in development as well as ongoing management and maintenance. More importantly it saves time
and allows you to accelerate your critical project deliveries to drive business outcomes quicker.

57% 30x
Average reuse = 57% for MuleSoft MuleSoft CPG customers = typical
CPG customers 30x reuse on individual APIs

You will benefit from:

↓ License Costs
↓ Dev / Mgmt effort

All contents © MuleSoft, LLC

↓ Project Delivery Time
API-Led Connectivity
Logical pattern outlining the layers of responsibility between API Consumer & API Provider
application(s) through a request/response pattern over the internet

Layer M/O API Request Controls API Response Controls

Channel M ● Presentation logic Channel ● Business data processing

application ● Business data validation Application ● Presentation logic
● Client application security context (e.g. ClientId/Secret to call API)
● State management
● Orchestration & aggregation Internet

API Response
API Request
Experience M Common controls ● Detection and mitigation of security threats ● Data redaction Common controls
layer (across all layers): (e.g. SQL/XML/JSON injection threat protection) ● Data mapping from (across all layers):
● IP block/allow list ● Channel security (authn & authz) Canonical to Experience ● Encrypt
enforcement ● Cross-Origin Resource Sharing (CORS) API data format configurations
● Schema ● Data mapping from Experience API to Canonical data ● Data loss prevention (core and/or payloads
validation formats controls) ● Protocol
● Spike control transformation
Process O* ● Rate limiting / ● Process level security (authn & authz) ● Orchestration & ● Header injection /
layer throttling ● Orchestration & aggregation (within and across aggregation (within and removal
● Caching business domains) across business domains) ● Audit
● Protocol ● Logging
transformation ● Exception
● Header injection / handling
removal
System M ● Routing (content ● System specific security (authn & authz) - fine-grained ● Business data validation
layer based) controls ● Data mapping to
● Audit ● Data mapping from Canonical to System specific Canonical data format
● Logging data formats ● Data loss prevention (fine-
● Exception ● Service-level composition, orchestration & grained controls)
handling aggregation
● Business data validation, processing &
fulfilment
● Connectivity to underlying database (SoR/SoE/SoI)

Application Application
A B
*Use is optional/conditional based on requirement for business level service orchestration and/or
All contents ©
aggregation ofMuleSoft,
data LLC
 API-Led Connectivity Controls
Controls are cross-cutting across data, security, mediation, QoS & support

Category Logical Control(s) Definition & Usage

● IP block/allow list enforcement

● Detection and mitigation of security threats
● Authentication These controls are utilised to better secure applications as well as the systems they are
Security &
● Authorisation accessing while ensuring compliance with a zero-trust security model as part of the end-to-
Compliance
● Cross-Origin Resource Sharing (CORS) end service chain.
● Data loss prevention
● Data redaction

● Business data validation

● Schema validation
These controls are used to ensure that valid data is being exchanged across the application
Data Integrity & ● Data mapping
network, perform transformation to/from any formats and/or protocols, aggregate data from
Transformation ● Protocol transformation
multiple data sources, and add or remove data from the messages being sent/received.
● Aggregation
● Header injection/removal

● State management
These controls are responsible for the coordination and arrangement of multiple services
● Orchestration
Mediation & exposed as a single aggregate service, ensuring message exchange sequences are
● Service-level composition
Connectivity controlled and coordinated, and provide the ability to connect to any data source with optional
● Routing (content based)
routing to different destinations based on the content of the input or output message.
● Connectivity to underlying database

● Spike control
● Rate limiting/throttling These controls are applied to ensure and preserve the end user experience, sustain and
Quality of Service
● Caching deliver SLAs, and ensure back end systems aren’t overly taxed and overloaded.
● Exception handling

Support & ● Audit These controls are used to provide visibility and traceability of all interactions across the
All Troubleshooting
contents © MuleSoft, LLC● Logging application network for support, troubleshooting, analytics and compliance.
 API Manager Policies (1/2)
Security

● OAuth 2.0 Access Token Enforcement: Configures the API so that its endpoints require a mandatory and valid OAuth 2.0 token
● Basic Authentication: Simple: Protects the API by requiring username and password when calling apps make a request
● Basic Authentication: LDAP: Establishes the configuration details for an Open LDAP or Active Directory LDAP that you set up for your enterprise
● IP Blocklist: Denies API calls from a defined set of IP addresses
● IP Allowlist: Limits API calls to a defined set of IP addresses
● JSON Threat Protection: Protects the target API against malicious JSON that could cause problems
● JWT Validation: Validates the signature of a JWT token and asserts the values of the claims of all incoming requests
● XML Threat Protection: Protects the target API against malicious XML that could cause problems.

Quality of Service

● HTTP Caching: Provides a way to store HTTP responses from an API implementation or an API proxy for later reuse
● Rate Limiting: Limits the number of messages processed by an API per time period at a maximum value specified in the policy. The rate
limiting is applied to all API calls, regardless of the source. Any messages beyond the maximum are rejected
● Rate Limiting – SLA-Based: Limits the number of messages per time period processed by an API at a maximum value specified in the
SLA tier. Any messages beyond the maximum are rejected. Enforcement is based on the client ID passed in the request.
● Spike Control: Smooths traffic by ensuring that within any given period of time, no more than the maximum configured requests are
processed.
An up to date view of API Manager policies can be found here: https://docs.mulesoft.com/api-manager/2.x/policies-policy-categories

All contents © MuleSoft, LLC 142

 API Manager Policies (2/2)
Troubleshooting

● Message Logging Policy: Logs a custom message with the information available between policies, proxy, or backend in any point of the
execution.

Transformation

● Header Injection and Removal: Adds headers to the request/response of the message or removes headers.

Compliance

● Cross-Origin Resource Sharing: Allows JavaScript XMLHttpRequest (XHR) calls executed in a web page to interact with resources from
non-origin domains. CORS is a commonly implemented solution to the "same-origin policy" that is enforced by all browsers.
● Client ID Enforcement: Enforces the requirement for calls to the API must include a valid client ID and client secret.

An up to date view of API Manager policies can be found here: https://docs.mulesoft.com/api-manager/2.x/policies-policy-categories

All contents © MuleSoft, LLC 143

API-Led Use Cases

The following slides provide API-led connectivity diagrams for the

following use cases:
● Demand Planning
● Order Management
● Central Finance
● Order Capture

All contents © MuleSoft, LLC

 Use Case #1 Demand Planning
Support the business in producing an accurate and reliable demand forecast

Business Flow:
● Obtain all product and associated
hierarchy information from the MDM
solution and make it available to various
systems including Demand Management.
● Obtain sales data from multiple
commercial ERP solutions (60+) which,
over time, will consolidate down into 2 (i.e.
SAP S4 HANA and D365).
● Provide sales data to the Data Hub and
obtain the resulting cleansed, rationalised
outputs.
● Provide the rationalised sales data to the
Demand Planner solution which will
produce the resulting forecasts and sales
& operations plans.
● Disseminate the forecasts to the Data Hub
for further business analysis and insights.

All contents © MuleSoft, LLC

 Use Case #1 Demand Planning
Applying API-led connectivity to provide an accurate & reliable demand forecast

Commercial ERPs

Legacy Data Hub

MDM S4
ERPs - n (DH) Demand Planning
Illustrative HANA

Governance & Security

Developer Portal
Legacy Data Hub Forecast
Experience MDM SAP D365
ERP API API API
API API API
APIs
<publish>

Operations (Logging, Monitoring etc)

SDLC Tools for Design & Delivery

Product
Process Data Sales per SKU
APIs per Location API Rationalised
Sales

<subscribe>
System Data Sales
APIs Hub API API

Data Hub
Demand Planning (DH)
Demand Planning 8 new APIs +
Legend:
n legacy ERP
All contents © MuleSoft,
New Reusable LLCBlock
Building Publish-Subscribe
 Use Case #2 Order Management
Support the business in producing an optimised sales network/logistics plan that is responsive to the real-time changes
in supply vs. demand
Business Flow:
● Obtain demand forecast generated by
Demand Planning and make this available
to Supply Network Planner.
● Obtain core inputs (sales orders, stock
info, despatch updates and equipment
capacity) from Commercial ERP &
Manufacturing ERP solutions.
● Integrate with Data Hub to provide core
inputs and obtain the resulting cleansed,
rationalised outputs.
● Provide rationalised sales data, stock
details, order info, & equipment details to
Sales Network Planner solution which will
facilitate further business inputs directly
within the Planner solution to produce the
Stock transfer proposals.
● Disseminate the stock transfer proposals
to the Data Hub for further analysis and
insights.
All contents © MuleSoft, LLC
 Use Case #2 Order Management - 1
Applying API-led connectivity to produce an optimised sales network/logistics plan
Commercial ERPs Commercial & Manufacturing ERPs
S4 S4
MDM HANA
HANA Demand Planning
Illustrative

Governance & Security

Developer Portal
D365 Forecast SAP D365
Experience MDM SAP
API API API API
API API
APIs
<publish> Sales, Stock, Despatches
&
Equip. Capacity

Operations (Logging, Monitoring etc)

SDLC Tools for Design & Delivery

Product
Process Data Sales & Stock
Orders per SKU
APIs per Location API Process API

<subscribe>
System SAP D365 SNP Data Hub
APIs API API API API

S4
HANA Data Hub
Supply Network Supply Network (DH)
Planner Manufacturing ERPs Planner
Legend:

All contents © MuleSoft,

New Reusable LLCBlock
Building Reused Building Block API Updates/Reusable Connectivity Continued …..
 Use Case #2 Order Management - 2
Applying API-led connectivity to produce an optimised sales network/logistics plan

Data Hub
(DH) Supply Network
Illustrative Planner

Governance & Security

Developer Portal
Data Hub SNP
Experience API API
APIs
Stock Transfer

Operations (Logging, Monitoring etc)

SDLC Tools for Design & Delivery

Rationalised sales data, Sales & Stock
Process stock details, order info, Process API
APIs & equipment details

System SNP Data Hub SAP

API API API
APIs

Data Hub S4
Supply Network (DH) HANA 5 Reused Assets + 3 API
Planner
Commercial & Manufacturing ERPs Updates + 3 New APIs
All contents © MuleSoft,
New Reusable LLCBlock
Building Reused Building Block API Updates/Reusable Connectivity
 Use Case #3 Central Finance
Integrate master data and journals/transactions from one or more source systems to Central Finance

Business Flow:
● Obtain all master data (customers,
vendors, GL account, cost element, cost
centre, material etc) from source systems
across markets and make it available for
Central Finance.
● Obtain all transaction/journals data (FI/
CO, CO Commitments) from source
systems deployed across markets and
make available for Central Finance.
● Provide master data to the Data Hub and
obtain the resulting cleansed, deduped,
rationalised outputs.
● Provide the rationalised master data to
Central Finance in a standard IDOC
format.
● Provide transactional data to Central
Finance in a standard IDOC format.

All contents © MuleSoft, LLC

 Use Case #3 Central Finance
Applying API-led connectivity to provide master data and journals/transactions to Central Finance

Data Hub
S4 Legacy (DH)
MDM
HANA ERPs - n
Illustrative

Governance & Security

Developer Portal
MDM SAP D365 Legacy Data Hub
Experience API API API ERP API API
APIs
<publish>

<subscribe> Transaction / journals

Operations (Logging, Monitoring etc)

data (FI/CO, CO

SDLC Tools for Design & Delivery

Process Rationalised
Customers Transactions Commitments) from
master data
APIs Customers, Vendors, GL Info API API markets
Account, Cost Centres, Materials

System
Data SAP API
APIs Hub API

Data Hub S4
(DH) HANA 5 API Updates +
Central Finance 2 New APIs

All contents © MuleSoft,

New Reusable LLCBlock
Building Reused Building Block API Updates/Reusable Connectivity
Driving Speed to Market with MuleSoft
Accelerating transformation of the supply chain
Project 3
Central Finance
13 Unique APIs
Project 2 21 Total APIs
Order Transactions API
Management (incl. multiple versions)
Customers Info API

Supply Network Planner API Supply Network Planner API

Project 1
Demand
Planning
Sales & Stock Process API Sales & Stock Process API 50% Faster project
delivery

Orders per SKU per Location API Orders per SKU per Location API

Sales API Sales API Sales API

Legend:
Sales per SKU per Location API Sales per SKU per Location API Sales per SKU per Location API

Forecast API Forecast API Forecast API New Reusable Building Block

Data Hub API Data Hub API Data Hub API Publish-Subscribe
Legacy ERP API Legacy ERP API Legacy ERP API Reused Building Block
Microsoft Dynamics 365 API Microsoft Dynamics 365 API Microsoft Dynamics 365 API
API Updates/Reusable Connectivity
SAP S4 HANA API SAP S4 HANA API SAP S4 HANA API

Master Data Mgmt (MDM) API Master Data Mgmt (MDM) API Master Data Mgmt (MDM) API
Time
8 New APIs 6 New/Updated APIs 7 New/Updated APIs

Complex Legacy Estate Composable Architecture

All contents © MuleSoft, LLC
 Legend: = Reusable Building Block

Use Case: Order Capture (D2C) = Message Queue

OMS plus other channels ( e.g. 'pick and pay', last mile
Illustrative logistics providers, customer service, retail chains etc).
Web App

Experience Web App Order Update

API API
Layer Order create/ Publish order
update update

Consume order event

Retrieve
Authentication Retrieve
products
customer details

Process Order API

Layer Customer API Product API

Create/update order

System Identity Salesforce HubSpot Magento SAP Salesforce HubSpot

Layer API API API API API API API

IAM Customer Customer eCommerce OMS Customer Customer

All contents © MuleSoft, LLC
MONITORING
IT monitoring is now more than a technology tool ….

It’s a business imperative.

The monitoring function safeguards the entire business reducing

risk, preserving the customer experience,
accelerating time to market, and lowering costs.
Monitoring Overview
Effective monitoring is needed at every level of an enterprise's IT landscape

End-Devices and Browsers Customer responsibility

UX monitoring, transactions and response times, page views etc

Services (Interfaces: APIs, events, batch processing etc)

Service availability, performance, response times, error rates, custom metrics etc
Tooling and data provided by
MuleSoft
Applications
Application availability, performance, security, error rates, custom metrics etc

IT Infrastructure (servers, virtualisation and containers, OS, disk storage)

Infrastructure resource capacity and utilisation, uptime, failure rates etc Managed by
MuleSoft as part
of CloudHub
Data Centre, Network and Security iPaaS offering
Switch and router utilisation, uptime, network bandwidth consumption, latency, vulnerability, intrusion detection etc
 Key:

MuleSoft Titanium vs Third-Party Monitoring Tools Optional integrations

MuleSoft Titanium provides application performance monitoring, log management & custom metrics
MuleSoft Anypoint Platform Anypoint Monitoring
provides 3rd party Third-Party Monitoring Tools
connectors on
Anypoint
Exchange
Service Management
tio ns
Ex cep

Application Performance
Log data Monitoring (APM)

Enterprise Log
Management

● Third-party enterprise monitoring tools typically used to perform high-

● Core Application Performance Monitoring, Log Management and
level event analysis and correlation across IT applications.
custom metrics all available and included with Titanium, which:
● Most enterprise monitoring tool vendors will have some form of OOTB
● Provides enhanced operational insights
and custom dashboards, but will require heavy customisation to
● Allows more informed decisions
support all metrics for Mule apps.
● Reduces mean time to identification
● Dedicated infrastructure price points will vary based on usage rages,
● Ensures high performance
where as Anypoint Monitoring with Titanium provides unlimited data
● Data can be offloaded/sent to third party solutions if required
storage and retention.
Working with 3rd party monitoring tooling isn't trivial
….. and can quickly lead to additional complexity

1 Build a custom app 2 Parse data into meaningful info 3 Operate, maintain and update

● Who will be writing the application to ● Do you know who will be in charge of ● Who will be in charge of keeping
forward data? parsing through the forwarded data? these custom applications up to
date?
● Have you thought about what types ● How many dashboards and metrics
data you need to forward? will you need to custom create? ● What happens if your log data
changes at any point in time?
● How many different monitoring ● How do you plan to measure metrics
solutions need data from Mule apps? native to Mule? (i.e. Connector ● What about change management?
metrics) How do you plan to handle version
changes?
HYPER-AUTOMATION &
EXAMPLES BY USE CASE
Hyperautomation
The new face of MuleSoft

✓ Artificial intelligence (AI)

“Hyperautomation is a
✓ Machine learning
business-driven, disciplined ✓ Event-driven software architecture
approach that organizations use ✓ Robotic process automation (RPA)

to rapidly identify, vet and ✓ Business process management (BPM) and

intelligent business process management suites
automate as many business (iBPMS)
✓ Integration platform as a service (iPaaS)
and IT processes as possible.”
✓ Low-code/no-code tools
✓ Packaged software

Gartner Top Strategic Technology Trend 2022 ✓ Other types of decision, process and task
automation tools
Build automations quickly but securely
The best of both worlds

Marketing

H
Service
R

Business Governance IT teams

teams & security

Ops Finance

Sales
MuleSoft is the ONLY unified platform for integration,
API management and seamlessly built into Salesforce
Business teams IT teams

Legacy

Images

Cloud
Docs

Governance On-prem
& security
Platform Events Custom

Pre-built Industry Flows

Salesforce
Flow
Omni-script

Netsuite Automate Everything.

Empower Everyone.
Jira

Salesforce
 [Customer] Hyper-automation Practice

Process Process Build Test & Monitor &

Deploy
Evaluation Design Automation Validation Operate

Anypoint Security

Anypoint Monitoring

Anypoint Exchange

Supporting Supporting
Business

Automation IT
API-First Automation Approach

MuleSoft RPA MuleSoft Composer & Flow Anypoint Platform

Human Task Automation Business Process Automation API-led system automation
Sharing RPA Sharing API Assets
Assets

Reuse Reuse
What we’ll prove

Can we demonstrate
Can we automate manual Can we modernize our
meaningful business impact
processes at speed? now and for the future? legacy leveraging RPA?
‘Automation’ Proofpoint = Payroll Ad Hoc Payments
Existing Workflow*
Manual, repetitive work leading to potentially wasted time & errors

Spidermail
action triggers Manual process without automation
request
Client Accounts Team

Copy/Paste to
Submit payment and
Manual
Check preferences & receive net / tax
Payments excel Next day
add to Pension details
Sheet submit to
Gateway (PG)
Withdrawls

Copy/Paste to Colleagu
Copy/Paste client Broker Focus e Manual
details to PG
Review

Challenges:

Longer than necessary time to complete - >1,000 minutes PM

Incorrect/inconsistent data

Business Impact:

Customer Satisfaction if errors & not scalable to daily payroll *Indicative & Simplified Diagram

Increased cost to serve

EXAMPLE - needs to be Colleague Satisfaction from unstimulating and repetitive tasks

tailored for customer
‘Automation Proofpoint = Payroll Ad Hoc
Payments - Solution Workflow

EXAMPLE - needs to be
tailored for customer
‘Orchestration’ Proofpoint = Estates Client Holdings
Existing Workflow*
Manual, repetitive work leading to potentially wasted time & errors
Death
Certificate Manual process without automation
Received
Colleague Update
Generate &
Manual Review Spidermail
distribute
If Yes → execute 12 correct
Estates Team

IVR complete &

different outcomes Produce documents
Master spreadsheet
updated Valuation

Double check
Check 12 locations Notify up to 6 other process is
for active accounts teams complete

Challenges:

Longer than necessary time to complete - >450 hours PM

Incorrect/inconsistent data at a critical moment of truth for client

Business Impact:

Customer satisfaction & risk of incorrect communications

Increased cost to serve / risk of AUM leaving platform

EXAMPLE - needs to be Colleague Satisfaction from unstimulating and repetitive tasks

*Indicative & Simplified Diagram
tailored for customer
‘Orchestration’ Proofpoint = Estates Client Holdings
Simplified Automation Workflow*
Reduce manual cost, data inaccuracy, and build future reusable asset

Automated Process

Generate Valuation
Estates Team

Receive Death Provide Client Holdings & Documents

Certificate view within Salesforce

Execute relevant Receive detail Trigger comms &

from other teams Update all
RPA Bots

Check all active decisions & add necessary systems documents to

to Salesforce & update to stakeholders
accounts
Salesforce

Notify other
teams as needed

EXAMPLE - needs to be *Indicative & Simplified Diagram

tailored for customer
Estates Collect Client Holdings - Simplified
Automated Workflow*
Reduce manual cost, data inaccuracy, and build future reusable asset

Automated Process

Generate Valuation
Estates Team

Receive Death Provide Client Holdings & Documents

Certificate view within Salesforce
Benefits:
Customers experience
Employee efficiency
Improved data accuracy
Business Impact:
Reduced cost to serveReceive detail
Execute relevant Update all Trigger comms &
fromstaff
other teams
RPA Bots

Check all active decisions &Satisfied

add customers and necessary systems documents to
to Salesforce & update to stakeholders
accounts Frees up staff to focus on high value tasks
Salesforce

Notify other
teams as needed

EXAMPLE - needs to be *Indicative & Simplified Diagram

tailored for customer
Customer Creation: Workflow Automation with MuleSoft
(CRM)

Flow 1 Flow 2

Listener
Composer

New Yes
Check for new Extract new
customer
customer record customer data Notify team that
found?
new customer
No record created
API call
RPA

Automatically create
customer record in
legacy system

EXAMPLE - needs to be
tailored for customer
CONNECTORS
Accelerate delivery while lowering costs &

Integrate systems
5x
faster with Anypoint
pre-built connectors
and accelerators
400+
Out of the box APIs, connectors, templates,
and accelerators

“With MuleSoft’s Anypoint Platform and the reusable connectors

we have built, we are accomplishing 33% more projects with
the same number of resources."
Senior Engineering Manager
Leading Online Marketplace
 Connectors, APIs and Accelerators
Examples of what to find on the MuleSoft Anypoint Exchange marketplace

Accelerators include a mix of

Architectures - “Accelerators” technologies assembled into
project-ready architectures
like: SAP (ECC & S/4) Salesforce
CRM, Service Cloud, Commerce
E2E Architectures for various integration Cloud, Jira, ServiceNow, MDM &
PIM Abstractions, Tableau, ..
scenarios
Example: https://www.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/1.6/

SAP SAP SAP SAP SAP

Accounts Pricing API Credit Memo Orders Bulk API
Underlying Tech: Synchronisation Templates =
SAP & Salesforce APIs & API Payable API API API
● Events (SF & S/4) bi-directional sync template for
Fragments Blueprints & Code-Examples SAP SAP
Products API Billing Docs
SAP Customer
System API
SAP Invoice
System API
SAP
Suppliers API ● Idocs (ECC, S/4) various objects (SF - SAP)
API ● RfC (ECC, S/4)
Aggregation Templates =
SAP Salesforce Salesforce Salesforce Salesforce Salesforce ● REST - Standard JSON,
Building blocks to adapt and re-use object aggregation (e.g. SF
Inventory API Contacts API Accounts API Marketing API Opportunity API Contract API OData or SOAP (SF, S/
customer + SAP Customer =
further fragments: https://www.mulesoft.com/exchange/? 4, ECC NW)
Salesforce Salesforce Salesforce Salesforce Synchronisation Aggregation aggregated customer object)
type=raml-fragment&type=rest-api
Orders API Case API Products API Pricing API Templates Templates

Connectivity:
● Certified connectors using native libraries
(e.g. SAP or Siebel) or provided APIs
Sharepoint
Connectors ● Abstraction of Interfaces
Filesystem
AWS Services
REST/SOAP ● Security - Authentication, Encryption, etc.
● Technical parameters (e.g. reconnect-
X12
Technology abstraction Azure
EDIFACT strategies, polling frequencies, etc.)
FTPS/SFTP Services Amazon S3
- extract MongoDB

Above diagram shows an excerpt of MuleSoft pre-built assets

All contents © MuleSoft, LLC

SAP Connectors
Power any system with real-time data from SAP
Prebuilt and Certified Connectors for SAP Netweaver and SAP S/4 Hana and SAP Cloud Services allow you to unlock
Data from your SAP Systems independent of where it resides

Simplify Development
MuleSoft’s Datasense™ Technology retrieves SAP Metadata required to develop APIs and simplifies development.

The connector supports:

● Inbound and outbound Remote Function Call (RFC) communication through Intermediate Document (IDoc) or
Business Application Programming Interface (BAPI).
● Synchronous, transactional, and queued RFC (sRfc, tRfc, qRfc protocols).
● Client connection pooling.

With this connector you can:

● Discover BAPIs using the Business Object Repository by specifying a specific business object, or a wildcard
containing a partial object name.
● Query BAPI/RFM enabled function modules by specifying the BAPI or Remote Function Module name.
● Send IDocs to, and receive IDocs from SAP by specifying the IDoc, including building the segment profile.
● Import IDocs with extensions and having the extra fields appear in profiles.
All contents © MuleSoft, LLC
MuleSoft Integration Templates for SAP
Go quickly from a blank canvas to a production application

Get up and running fast

● Maximize speed while retaining flexibility to tailor templates
to your unique needs

Solve common integration use cases

● Between SAP ERP, S/4HANA, Hybris, Salesforce,
and Workday

Leverage best practices

● Templates are designed, tested, and productized based on
our work with hundreds of customers

Simplify SAP to Salesforce integration +64%

faster project
delivery
● Templates to sync, move, and update account and product
data between the two systems in bulk or real-time

All contents © MuleSoft, LLC

HTTP(S) Connector
Power any system with real-time data exchanges over HTTP(S)

Anypoint Connector for HTTP (HTTP Connector) enables you to declare HTTP servers that listen to requests and
trigger flows, as well as HTTP clients that can communicate with any HTTP service.

HTTP Servers:
● Expose services for users or applications to consume.
● Services receive data in the form of requests and return corresponding responses. API Consumers
● HTTP Listener source triggers flows when a request is received and responds after
the flow finishes.

HTTP Clients: Application

Network
● Send requests to HTTP services and manage their responses.
● HTTP Request operation executes HTTP requests and returns the
corresponding answers.

All contents © MuleSoft, LLC

WHY MULESOFT?
Why is Mule best placed for Salesforce Projects?
MuleSoft enables your organisation to deliver Salesforce projects faster, with less effort and less risk.

Reduced
Faster Project Lower Risk
Implementation
Delivery
Costs

Leverage Salesforce accelerators to Remove risk associated with

Reduce time to market for downtime and starting from scratch
Salesforce projects save 100’s of man-days effort
 Faster Project Reduced
Lower Risk
Delivery Implementation Costs

● Pre-built Mule integration ● Accelerators help remove 100’s ● 99.99% SLA availability
accelerators for Salesforce clouds of hours of design & development compared to 99.9% in Azure/
Example: Service Cloud effort AWS* (equivalent to ~45mins a
Accelerator month downtime using Azure/
● Potential reuse of APIs/assets AWS vs ~4 mins with MuleSoft)
● Unrivalled out of the box from existing projects leveraging
connectivity to Salesforce Clouds MuleSoft ● Templates & Accelerators ensure
Example: MuleSoft Connector Mule best practices are baked in
Exchange vs built from scratch
● Proven enterprise reliability for
large projects with over 50bn
transactions a month globally

*Assumption Azure/AWS configured for 99.9% availability

Path to #1 in Every Category
Leader in iPaaS and Full Lifecycle API Management, Visionary in RPA

Full Lifecycle Robotic Process

iPaaS API Management Automation (RPA)

8x 7x Visionary
Leader Leader
MuleSoft Named a Forrester Leader
Forrester Leader in iPaaS and API Management Solutions Waves

iPaaS API Management

3x 1x
Leader Leader
MISCELLANEOUS
What is a Digital Product?

“You’ve got to start with

the customer experience
and work back toward
the technology — not
the other way around.”

— STEVE JOBS

All contents © MuleSoft, LLC

Synergies between Industrial & Digital Supply Chains

Industrial Supply Chain

Sourcing Manufacturing Distribution Sales Consumption

Digital Supply Chain

Discovery Development Deployment Registration

184 Experience
(of Data & Services) (of Digital Solutions) (of Digital Solutions) (by Customers) (by customers)

All contents © MuleSoft, LLC

Digital Products

Feel like physical products …

● Serve and generate customer demand
● Fulfill a related set of tasks
AP
● Manufactured, released, marketed, distributed I

AP
I
but are different ...
AP
I
● Provide an experience, not material goods
AP
● Can change in the customer’s hands I

● Powered and differentiated by software

AP
I
All contents © MuleSoft, LLC
Digital Products in the Ecosystem

The primary goal of Digital Products is to

establish and continuously improve a
sustainable business model that serves groups
of API consumers and customers by providing a
useful service that provides value along with
connected seamless digital experience

All contents © MuleSoft, LLC

API Product Ecosystem

All contents © MuleSoft, LLC

API Benefits
# BENEFIT HOW AN ECOSYSTEM MAKES THE BENEFIT REAL

1 FOSTER OUTSIDE-IN THINKING The ecosystem perspective helps you establish a customer- driven view of your API and its value
proposition

2 DETERMINE THE BUSINESS Outlining the overall ecosystem helps you understand the best business model for your API
MODEL products that optimizes value for customers and value for your organization.

3 DRIVE THE RIGHT CONSUMPTION Knowing the business model means knowing what API consumption profile to aim for and how to
incentivize that consumption.

4 IDENTIFY NEW CHANNELS & Getting a picture of your API ecosystem helps to identify channel gaps and potential new customer
SEGMENTS segments.

5 CREATE NEW CONSUMER VALUE Seeing how value flows in the ecosystem will enable you to find new opportunities to create and
deliver value to customers.

6 OPTIMIZE DIGITAL SUPPLY CHAIN Understanding the dependencies of your API will help to find potential efficiency gains.

7 FACILITATE INNOVATION Mapping the API ecosystem for your API products and even your partners’ and competitors’
ecosystems will help you take advantage of all innovation opportunities.

8 CO-CREATE VALUE WITH Visualizing the API ecosystem can facilitate pattern matching of API co-collaboration archetypes.
PARTNERS

9 ESTABLISH FEEDBACK LOOPS

All contents © MuleSoft, LLC
Examining the ecosystem from a system dynamics perspective can help you deeply understand the
impacts of changes to the ecosystem and manage accordingly.
5 Keys to a Great API
Each ‘key’ has two sides - business and technology

1. A valuable service (data, function, audience)

2. A plan and a business model
3. Simple, flexible and easily adopted
4. Managed and measured
5. Great developer support

All contents © MuleSoft, LLC

Top 10 API Worst Practices

1. Poor error handling

2. Rest APIs that ignore HTTP rules
3. Exposing your raw underlying data model
4. Security complexity
5. Unexpected and undocumented releases
6. Poor dev experience
7. Expect an MVC framework ‘gives’ you a great API
8. Assume if you build it they will come
9. Inadequate support
10.Poor documentation

All contents © MuleSoft, LLC

KEY RESOURCES
 Key Resources - MuleSoft
Key assets to support the architecture slides and templates presented in this deck

# Title / Link Comments

1 API Strategy Template Customer-facing

2 Enterprise Integration Patterns Customer-facing

3 UKI SCA Architecture PoV Library Internal

4 SE MuleSoft 101 Template Deck Internal

5 Jeroen Reizevoort Slide Deck Customer-facing

6 API Strategy in a MAD World (Mergers, Acquisitions & Divestitures) Customer-facing
7 MuleSoft Architect Webinar on Event Driven Architecture (EDA) Customer-facing
8 MuleSoft Demos in a Deck Customer-facing
9 SAP SE Slide Assets Customer-facing
10 MuleSoft Security Enablement Internal-facing
11 Business Process Management Whitepaper Unknown
12 B2B/EDI with Anypoint Platform Customer-facing
13 MuleSoft RPA Customer-facing

All contents © MuleSoft, LLC

Cont'd….
 Key Resources - MuleSoft
Key assets to support the architecture slides and templates presented in this deck

# Title / Link Comments

14 Delivering composability & reuse with MuleSoft Customer-facing

15 MuleSoft IoT Use Cases Customer-facing

16 MuleSoft Platform Capability Matrix Internal - Confidential

All contents © MuleSoft, LLC

Cont'd….
 Key Resources - Salesforce
Key assets to support the architecture slides and templates presented in this deck

# Title / Link Comments

1 Salesforce Enterprise Architecture Capabilities Internal

2 Salesforce Architecture Diagram ToolKit Internal

3 Salesforce Platform - APIs & Integration Capabilities Internal

4 Interactive Guide to Integrations at Salesforce Customer-facing
5 Build vs Buy: A framework for deciding the best course of action for your business Customer-facing
6 Salesforce Data Strategy Customer-facing
7 An Intro to Enterprise Architecture Customer-facing
8 Architecting with Salesforce Data Cloud Customer-facing

All contents © MuleSoft, LLC

 Key Resources - MuleSoft & Salesforce
Key assets to support the architecture slides and templates presented in this deck

# Title / Link Comments

1 MuleSoft and Salesforce: One Stop Shop Customer-facing

2 Connecting to CDP with Anypoint Platform Customer-facing
3 Salesforce Tableau Slack MuleSoft Data Integration PoV Internal

All contents © MuleSoft, LLC

 Key Resources - Competitive PoVs
Key assets to support the architecture slides and templates presented in this deck

# Title / Link Comments

1 MuleSoft vs Azure: What's the difference? Customer-facing

2 Architecture Insights into Azure APIM vs MuleSoft Flex Gateway Customer-facing

All contents © MuleSoft, LLC

 Key Resources - Industry PoVs
Key assets to support the architecture slides and templates presented in this deck

# Title / Link Comments

1 Smart Manufacturing with MuleSoft in Consumer Goods Orgs Customer-facing

2 Customer X: ERP Transformation Journey Customer-facing
3 Mergers & Acquisitions in Banking Internal
4 Supply Chain Modernisation Customer-facing

All contents © MuleSoft, LLC

SOME FUN 'API' JOKES
(Warning: these jokes may seriously damage your sense of humour!)
API Joke #1

An API is like a joke…….

……. if you have to explain it, it isn't very good!

All contents © MuleSoft, LLC

API Joke #2

Why was the API feeling sleepy?

……… because it was RESTful!

All contents © MuleSoft, LLC

API Joke #3

Why doesn't an API have a passport?

……… because it's stateless!

All contents © MuleSoft, LLC

API Joke #4

Why did the API walk into a bar?

……… APIs shouldn't be able to walk into a bar as they

need to be managed, controlled, secured and governed!

All contents © MuleSoft, LLC

Joke #5

All contents © MuleSoft, LLC

Joke #6

All contents © MuleSoft, LLC

Joke #7

All contents © MuleSoft, LLC

Joke #8

All contents © MuleSoft, LLC

 &

Questions ?
Questions?
APPENDIX
Anatomy of a MuleSoft Building Block

API Governance
Policies
Permissions
Customer ID Order history Analytics

Contract
RAML / OAS / SOAP SecuritySchemes
API policy Traits Reusable properties
ResourceTypes
API contract
Business Logic

Logic Routing Aggregation

Enrichment Parallel execution
Transformation Splitting
Connectivity Validation

Connectivity
MQ, Database, SOAP, HTTP, SaaS, On-Prem
Customer orders Protocol implementation
Connections/resources management
Pooling
All contents © MuleSoft, LLC
Architecture Workshops

# Workshop Description

Design thinking & CURE (Customer Context, Unbundle, Reach, Extend) workshop used to
API Strategy
1 teach individuals the value of APIs so they can adopt a successful API strategy in their
Workshop
organisation.

Workshop which allows customers to understand how they can architect a composable
Architecture
2 business by following the MuleSoft approach to API-led connectivity, the value this provides
Workshop
and how this can be achieved using the Anypoint platform.

Session focuses on value of data, capabilities that enable an intelligent business, how this
Data Strategy
3 relates to composability, what makes a successful digital data strategy, and the role of data in
PoV
the wider data and Salesforce ecosystems. 210

All contents © MuleSoft, LLC