Microservices & anypoint service mesh calgary mule soft meetup

All contents © MuleSoft Inc.
June 17, 2021
APIs, Microservices & Anypoint
Service Mesh
Matt McLarty, Global Leader of API Strategy
Ganesh Iyer, Principal Solution Engineer

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

Meeting Logistics
● The session is recorded and a copy will be published to the meetup page
● Attendees are placed on mute upon entry
● Feel free to post your questions in the chat and we will answer them as we go
● We will have 3 trivia questions between segments and the winners will be
announced at the end
● Instructions will be provided before the trivia questions for valid participation
● Prize: each winner will get a voucher for a free MuleSoft course
3

Meeting Agenda
● Speakers introduction
● The implementer’s view
● The API and Microservices Landscape
● Q&A Part 1
● Anypoint Service Mesh Concept
● Demo
● Q&A Part 2
● Announcing Trivia Winners
4

About the Speakers...
● Global Leader, API Strategy, MuleSoft
● Based in Vancouver
● O’Reilly author
About Matt
● Principal Solutions Engineer
● Based in Mississauga
● 20+ Years in the integration space
About Ganesh

The Implementer’s View
● How granular should microservices be?
● How is service mesh different from API gateways?
● Can they be used together?
● How should microservices/APIs be secured?
● What is a good use case for Anypoint Service Mesh?
● What are some best practices for Anypoint Service Mesh?
● How flexible is the deployment of Anypoint Service Mesh?
6
Mandy Wong
Suncor

The Legacy of APIs and Microservices
7
The Web
Web Services
J2EE
SaaS
IaaS
Cloud Native Mobile
Agile
CI/CD
DevOps
Microservices
SOA
VM’s
Containers
Social
Networks
Serverless
APIs
Rails
JavaScript

The API and Microservices Landscape
From https://www.apidays.co/api-landscape
From https://landscape.cncf.io/images/landscape.png

Application Network
Mobile Shopping
API/Service
Orders
API/Service
Recommendations
API/Service
Inventory
API/Service
Product Catalogue
API/Service
Payment
API/Service
Access Control
API/Service
Customer Management
API/Service
Shipping
API/Service
3rd Party Shipping
API/Service
3rd Party CRM
API/Service
Legacy Orders
Application
Legacy IdM
Application
Mobile
Shopping App

All contents © MuleSoft Inc. 10
Application Network Planes
From http://networkstatic.net/the-control-plane-data-plane-and-forwarding-plane-in-networks/
Concept of “planes” (layers in the network)
popularized in SDN:
Data Plane - Business information ﬂow
Control Plane - Network metadata
In the Application Network, the Data Plane
consists of the API interactions that execute
business capabilities (e.g. place order,
check account balance)
The Control Plane consists of interactions
that execute technological capabilities
(e.g. monitoring, security, SLA management)

API & Integration Capabilities
API Consumer
Management
API Product
Management
Data Distribution
API Runtime
Management
API Design &
Development
● Sign-up & provisioning
● Sandbox & API simulation
● Community collaboration
● API directory & documentation
● API product design
● Plans & pricing
● Versioning & release management
● SLA/policy management
● Portfolio management
● Data classification
● System modeling
● Interface design
● API adaptation
● API development facility
● API testing facility
● API virtualization
● API deployment pipeline
● Traffic management
● Access control & policy
enforcement
● SLA enforcement
● Exception handling & recovery
● Monitoring & metrics
● Aggregation, federation &
virtualization
● Batch/bulk data loading
● Synchronization
● Tokenization & obfuscation
● Event driven messaging
● Data transformation
● Protocol translation
Task & Process
Automation
● Workflow definition &
management
● Analog data extraction
● No/low code composition
● Proprietary connectivity (SaaS,
COTS)
● Industry standards support (e.g.
EDI, FHIR)

Capability Implementations
API Consumer
Management
API Product
Management
Data Distribution
API Runtime
Management
API Design &
Development
Task & Process
Automation
API Developer Portal
API Community
Manager
API Manager (Portal
Admin View)
API Design Studio
Cloud
IDE
API IDE
API Gateway
Service Mesh
ESB
ETL
Event
Bus
No/Low
Code
BPM
RPA
B2B
Gateway

Application Network and Subnets
k8s-based domain
Event-driven
Serverless

Local
capabilities
L
o
c
a
l
c
a
p
a
b
i
l
i
t
i
e
s
Local
capabilities
Application Network and Subnets
Network-wide capabilities

Network-wide Capabilities
API Consumer
Management
API Product
Management
API Runtime
Management
API Design &
Development
● Sign-up & provisioning
● Sandbox & API simulation
● Community collaboration
● API directory & documentation
● SLA/policy management
● Portfolio management
● System modeling
● Traﬃc management
● Access control & policy enforcement
● SLA enforcement
● Monitoring & metrics
Uniﬁed
Platform

Service Mesh
Image from https://blogs.mulesoft.com/dev-guides/microservices/what-is-a-service-mesh/
● Packaged capabilities
○ Traﬃc management
○ Access control & policy
enforcement
○ SLA enforcement
○ Monitoring & metrics
● Deployment evolution
○ Shared libraries → sidecar
● Distinct path from API
Management/Gateway

17
APIs & Microservices Key Takeaways
● APIs and microservices exist in a vast, complex, converging landscape
● The “application network” concept helps ﬁlter noise and abstract the
complexity
● The application network’s “control plane” consists of a set of technological
capabilities
● These capabilities help to further understand the API and microservices
landscape
● A service mesh is a packaged implementation of some of these capabilities,
deployed in a container-based infrastructure

Trivia Questions - Rules & Regulations
1. Please ensure that you provide ONE answer
in the chat after:
- We have stated the question and all of the
options.
- Jimmy types “Go Now!” in the chat box.
2. You can type A, B, C, D in the chat section.
- Only one answer per person!
18

Trivia Question #1
In which API Management capability category would you classify “API
documentation”?
A. API Design & Development
B. API Consumer Management
C. API Product Management
D. API Runtime Management

Trivia Question #2
Which of the following capability implementations is classified under API Runtime
Management?
A. API Gateway
B. API Developer Portal
C. RPA
D. ETL

Q&A Part 1
● How granular should microservices be?
● How is service mesh different from API gateways?
● Can they be used together?
● How should microservices/APIs be secured?
21

23
Discover, manage and secure any service
Discover and leverage any
service
Maximize adoption and reuse by adding
microservices to Anypoint Exchange
Centrally manage from a
single platform
Bring API management and analytics to
microservices -- no matter the language or
cloud
Enable security by default
Implement zero-trust and ensure high
availability with traffic control policies
Anypoint Service Mesh

How it works
Anypoint Platform
API-led connectivity for microservices
Internal & External APIs
Discover Manage Secure
Service A
Sidecar
proxy
Service B
Sidecar
proxy
Mule Adapter
Istio
Kubernetes cluster
Mule applications
Mule Apps Mule Apps
CloudHub Runtime
Fabric

Extending the application network to any service
25
• Empower your customer teams to build according to their strengths
• Accelerate microservice adoption with auto-discovery and re-use
• Maintain ﬂexibility: it bends, not breaks – built for change

Anypoint Service Mesh Architecture
KUBERNETES CLUSTER (AKS/EKS/GKE/OpenShift)
HTTP/S
MANAGEMENT
CENTER
Service
A
Service
B
Envoy
Mule Adapter
API
MANAGER
API
ANALYTICS
Envoy
1
2
1
3 3
EXCHANGE
HTTP/S
namespace
a
b

API Management for Non-Mule Services
• Expose microservices as APIs in Anypoint
– Support for auto-creation from Kubernetes command line
OR
– For design-first approach- Publish APIs via API or UI and then use
auto-discovery ID for binding
• Apply mule policies from API Manager
• Istio policies (Request routing, circuit breaker, A/B..) are available
though its own control plane
• Services health can be monitored using API Analytics
• Non-mule assets can be discovered & reused from Exchange

Deployment Architecture
45

All contents © MuleSoft, LLC
Google Slides does not have an
image placeholder option. Please
place an image over this box
manually or work in
47
Director - Innovation
Technology
Jackie

50
Anypoint Service Mesh Key Takeaways
● A Service Mesh helps make service-to-service communications secure, fast
and reliable
● Service Mesh is essential to companies adopting a microservices architecture
at scale
● Service Mesh and API Management are complementary, and can be used
together to govern and manage all services at scale
● Anypoint Service Mesh extends the beneﬁts of the application network, and
gives you one single uniﬁed platform to discover, manage and secure any
service

Trivia Questions - Rules & Regulations
1. Please ensure that you provide ONE answer
in the chat after:
- We have stated the question and all of the
options.
- Jimmy types “Go Now!” in the chat box.
2. You can type A, B, C, D in the chat section.
- Only one answer per person!
51

Trivia Question #3
Which statement is Not True about Anypoint Service Mesh
A. You can expose non mule microservices as APIs in Anypoint
B. You can apply Mule policies from API Manager
C. You can visualize microservice dependencies using the application network
graph
D. Anypoint Service Mesh comes with its own kubernetes cluster with Istio
preconfigured for simplifying deployment

Q&A Part 2
● What is a good use case for Anypoint Service Mesh?
● What are some best practices for Anypoint Service Mesh?
● How flexible is the deployment of Anypoint Service Mesh?
53

Trivia Winners

Trivia Question #3
Which statement is Not True about Anypoint Service Mesh
A. You can expose non mule microservices as APIs in Anypoint
B. You can apply Mule policies from API Manager
C. You can visualize microservice dependencies using the application network
graph
D. Anypoint Service Mesh comes with its own kubernetes cluster with
Istio preconfigured for simplifying deployment

Thank you

Independent Services
Hybrid Deployment Model
62
Runtime Fabric CloudHub
Server
r
Mule
App
Worker
cloud
Control plane
Server
App App
Mule
App
YOUR NETWORK
Control plane Control plane
YOUR NETWORK
Istio
Kubernetes cluster
Mixer Mule Adapter
Service
Service
Anypoint Runtime Fabric
Server Server
Runtime Fabric services
Docker & Kubernetes (nodes)
Mule
App
Mule
App
Mule
App
Mule
App

Anypoint Runtime Fabric
Server Server
Runtime Fabric services
Docker & Kubernetes (nodes)
Mule
App
Mule
App
Mule
App
Mule
App
Anypoint Platform
API-led connectivity for microservices
Internal & External APIs
63
Discover Manage Secure
Flexible Deployment
Server
App App
Mule
App
r
Mule
App
Worker
cloud
Service A
Sidecar
proxy
Service B
Sidecar
proxy
Istio
Kubernetes cluster
Mule Adapter
YOUR NETWORK
Mulesoft Cloud

Microservices & anypoint service mesh calgary mule soft meetup

More Related Content

What's hot (20)

Similar to Microservices & anypoint service mesh calgary mule soft meetup (20)

Recently uploaded (20)