Raleigh MuleSoft Meetup - October

John Lanuti, MuleSoft Solution Engineer
Anypoint Platform
October 2019 Release
John Lanuti, MuleSoft Solution Engineer
Anypoint Platform
October 2019 Release

All contents © MuleSoft Inc.
Safe harbor statement
The information in this presentation is confidential and proprietary to MuleSoft and may not be
disclosed without the permission of MuleSoft. This presentation is not subject to your license
agreement or any other service or subscription agreement with MuleSoft. MuleSoft has no obligation
to pursue any course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related presentation
and MuleSoft's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by MuleSoft at any time for any reason
without notice. The information on this document is not a commitment, promise or legal obligation
to deliver any material, code or functionality. This document is provided without a warranty of any
kind, either express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement. This document is for
informational purposes and may not be incorporated into a contract. MuleSoft assumes no
responsibility for errors or omissions in this document, except if such damages were caused by
MuleSoft intentionally or grossly negligent.
All forward-looking statements are subject to various risks and uncertainties that could cause actual
results to differ materially from expectations. Readers are cautioned not to place undue reliance on
these forward-looking statements, which speak only as of their dates, and they should not be relied
upon in making purchasing decisions.
2

All contents © MuleSoft Inc. 3
Benefits of MuleSoft’s Anypoint Platform
Fast to start,
faster over time
ACCELERATED
DELI VERY
Security and
governance by default
AUTOMATED
SECURI TY
Built-in reliability,
scalability, and visibility
RESI LI ENT
OPERATI ONS
Flexible and
built for change
FUTURE-PROOF
FOUNDATI ON

All con t en t s © Mu leSoft I n c.
Applying API-led connectivity to B2B transactions
5
Process
APIs
LOB IT Purchase Order Invoice Shipping Notice
System
APIs
Central IT
Business processing
(partner agnostic)
Partner 1 Partner 2
Experience
APIsLOB /
Central IT
API EDI 850 EDI 810 EDI 856
Message mappings
(partner specific)
Partner 1 Partner 2
eCommerce
Products API Orders API Partner API

All con t en t s © Mu leSoft I n c.
Overview of capabilities in MuleSoft’s B2B solution
6
• Web-based modelling to
on-board partners, configure &
validate documents, & define
security.
• Dataweave-based mapping
• Manage certificates
• Support for Hybrid deployment
model
Par t n er Set u p an d
Man agem en t
• Support for “inbound / Receive”
transactions via X12 EDI
• Support for transport protocols -
AS2 and SFTP
Tr an spor t an d Ex ch an ges
• Audit tracking leveraging core
Anypoint platform capabilities
• Track high-level B2B operational
metrics such as # of messages
and # of errors (i.e. messages
received, versus processed,
versus failed).
Tr an sact ion Repor t in g

Choosing microservices is the easy part...
1212
Isolated
expertise
Siloed management and
governance
Custom coded network configs
Inconsistent
security across
services
99%
of organizations adopting
microservices report
challenges*
*Source: 2018 Global microservices trends report
https://go.lightstep.com/global-microservices-trends-report-2018
SAP

Discoverability and governance with a service mesh
13
Gain visibility across services
Focus on business logic
Ensure resiliency with traffic control
Implement zero-trust security
Service A
Sidecar
proxy
Service B
Sidecar
proxy
Mixer Adapter(s)
Service mesh
Kubernetes cluster
Ingress
Service C
Sidecar
proxy
UI

Anypoint Platform
API-led connectivity for microservices
Internal & External APIs
14
Discover Manage Secure
How it works
Service A
Sidecar
proxy
Service B
Sidecar
proxy
Mixer Mule Adapter
Istio
Kubernetes cluster
Controller
Anypoint Runtime Fabric
Edge
Ingress
Ingress
Worker Worker
Mule Apps Mule Apps
14

Extend API management to every microservice
15

Monitor multi-cloud environments from one view
16

Maximize adoption with Anypoint Exchange
17

API Delivery Cycle
Lessons from the Real World

Friends, don’t let friends write java code
• Dataweave Sample

API Led Connectivity
• Experience APIs
• Process APIs
• System APIs

Review
• Let’s do a review of the basics of API-led connectivity.
24

• Order data in eCommerce system
• Inventory data in SAP
• Customer data in SAP, Salesforce
Project objective: Web app
provides real-time order status and
order history for sales team
engaging with customers
A common project-based approach
Aggregated
customer data
Order status Order history
Web app API
25

A common project-based approach
Web app API
Aggregated
customer data
On time and within budget
Limited opportunity for reuse
Tight coupling = brittleness
Difficult to govern
Meets business requirements?
26

Integration project
6 months later…
Aggregated
customer data
mobile APIMobile API
Aggregated
customer data
Order historyOrder status
Web app APIWeb app API
27

The API-led connectivity approach
System
APIs
Process
APIs
Experience
APIs
Customers
Web app API
Orders
Salesforce
customers
SAP
customers
Order
status
Order
history
28

The API-led connectivity approach
System
APIs
Process
APIs
Experience
APIs
Customers
Web app APIMobile API
Orders
Salesforce
customers
SAP
customers
Shipment
status
Toll
shipments
UPS
shipments
Order
status
Order
history
29

Process APIs Resemble the Entities of an ERD
• Resembles a logical data model for your organization

System APIs should use canonical business data
• One system API for each back end data source.
• System APIs should look like canonical business data so they can be easily interchanged.
• Do not simply create a proxy for a back end system.
• Do not make the process API developers learn the semantics of a back-end system.
Exact Target Inputs
• Index Name
• Query
System API Resources
/query:
QueryParams:
Index Name
Query
Exact Target Inputs
• Customer info
System API Resources
/customer:
QueryParams:
firstName
lastName

Create a Connectivity Protype Early
• It can sometimes take a long time connect to back end systems
(especially for system APIs).
• Create the connectivity prototype early in the project.
38

Connectivity prototype
• Done in parallel
with design
• Saves time and
eliminates
surprises
APIDeliveryProcessSummary
ArchitectAPIDesignerAPIDeveloperAPIConsumer
Identifya need
Determine the
Architectural
Approach
API Design, API
Portal in Exchange
Connectivity
Prototype
API Development
and Testing
Update Base URI
DeployAPI, Secure,
Setup Alerts
Review API Design
and Provide
Feedback
Request Access Consume API
No
Design Meets
Requirements
Yes
Wait

Have an API Delivery Checklist
• An API Delivery Checklist ensures that the work for each API is
complete and consistent
• Sample Checklist
40

Summary
• Friends, don't let friends write java code
• Process APIs Resemble Entities of an ERD
• System APIs should return canonical business data
• Create a Connectivity Prototype
• Have an API Delivery Checklist
41

Raleigh MuleSoft Meetup - October

More Related Content

What's hot

Similar to Raleigh MuleSoft Meetup - October

Recently uploaded

Raleigh MuleSoft Meetup - October

Editor's Notes