MuleSoft Sizing Guidelines - VirtualMuleys

All contents © MuleSoft, LLC
Mulesoft Composer
Anu Vijayamohan
Today!!
18:00 Europe/CET | 17:00 UK/GMT | 22:30 Delhi, India/IST
9:00 San Francisco/PST | 12:00 New York

Virtual Muleys Meetup
(Online Group - English )
Moderator: Angel Alberici
Meetup Edition, 2022
Recording
66

Virtual Muleys Meetup (Online Group - English)
9
9

PreReq: a current MuleSoft Certified Developer – Level 1 (Mule 4) certification.
Validates that a developer has the required knowledge and skills to:
● Expose production-ready Anypoint Platform-managed APIs from
Mule applications.
● Implement maintainable and modular Mule applications and
their Maven builds.
● Implement monitorable Mule applications.
● Implement performant and reliable Mule applications.
● Secure data at rest and in transit.
See certification details: mule.is/MCD-L2
MuleSoft’s first level 2 certification.
[NEW] Announcing MuleSoft
Certified Developer - Level 2
See all of our training and certification offerings
at training.mulesoft.com
Coming
end of
April!

MuleSoft Training
● 3 Day Fundamentals - We are now offering a 3 days version of the Development: Fundamentals
course, which requires learners to have completed an Intro to Anypoint Platform Workshop or the
Getting Started with Anypoint Platform course.
● Earn a certification attempt - Learners will be able to earn their MCD - L1 (Mule 4) certification
attempt by completing the self-paced “Anypoint Platform Development: Fundamentals” course. The
exam will then appear in their learner dashboard for scheduling.
● Flex - The training team are now offering ‘Flex’ courses which take place over a weekend or broken
up over half days.
14

● Check it out:
https://help.mulesoft.com/s/article/Mul
eSoft-Recommended-Support-Process
● Best practices guidelines on how to
troubleshoot
● Clear recommendations on how to best
work with Cases
● Most Common Troubleshooting
techniques for each Product
● And more!
Do you raise Support Cases to MuleSoft Support?

[March 31st Release] Anypoint Studio 7.12 Release Notes
16
https://docs.mulesoft.com/release-notes/studio/anypoint-studio-7.12-with-4.4-runtime-release-notes

[March 31st Release]: MuleSoft Accelerator for Manufacturing
17
https://www.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/
minor/1.0/pages/Use%20case%201%20-%20Run-rate%20business%20management/

[March 21st Release] Anypoint DataGraph Release Notes
18
https://docs.mulesoft.com/release-notes/datagraph/anypoint-datagraph-release-notes#march-21-2022

New API gateway and API manager experience
Extend Anypoint Platform to all APIs with the new ultrafast Anypoint Flex Gateway
Built for developers
● Manage locally with declarative
conﬁguration ﬁles
● Deploy anywhere - with support for
cloud instances, container
orchestrators, Kubernetes, and bare
metal
Loved by enterprises
● Apply pre-built or custom policies to
individual or groups of APIs with a
guided experience
● Centrally manage, secure, and observe
all APIs across the enterprise
Flex Gateway
API Manager
GA
H1 ‘22
Update
H1 ‘22
API Gateway Instance on Physical / VM
Azure
VM
Amazon
EC2
GCP Compute
Engine
Container sidecar / Ingress Controller

https://www.mulesoft.com/lp/reports/connectivity-benchmark
MuleSoft Benchmark 2022 Report is now available!

MuleSoft Sizing Guidelines
Anu Vijayamohan
Customer Success Technical Architect, EMEA

Agenda
1. Core Concepts of Sizing
2. Factors That Impact Mule Sizing
3. Sizing Nuances in Cloudhub vs OnPrem vs Runtime Fabric
4. T-Shirt Sizing
5. High Availability

Core Concepts of Sizing

What is a Mule Application?

What is a Flow?
Mule Flow
25

What is a Transaction?
26

Deployment: On-Premise
27
Standalone Mule Install
Server
App App
Mule
App
Control plane
YOUR NETWORK

Runtime Fabric
Deployment: On-Premise, Runtime Fabric,
Standalone Mule Install
Server
App App
Mule
App
Control plane
YOUR NETWORK
Control plane
YOUR NETWORK
Anypoint Runtime Fabric
Server Server
Runtime Fabric services
Mule
App
Mule
App
Mule
App
Mule
App
Docker K8s

Runtime Fabric
Deployment: On-Premise, Runtime Fabric & CloudHub
29
Standalone Mule Install CloudHub
Control plane
Server
r
Mule
App
Worker
cloud
Server
App App
Mule
App
Control plane
YOUR NETWORK
Control plane
YOUR NETWORK
Anypoint Runtime Fabric
Server Server
Runtime Fabric services
Mule
App
Mule
App
Mule
App
Mule
App
Docker K8s

Monolith
Mule Runtime (Ex 1 core)
Account Salesforce API Account SAP API Account Billing DB API
30
Runtime Considerations

Microservice
Mule Runtime
(Ex 1 core)
Account Salesforce API
Mule Runtime
(Ex 1 core)
Account SAP API
Mule Runtime
(Ex 1 core)
Account Billing DB API
31
Runtime Considerations

vCores vs Cores
“A vCore is equivalent to the number of CPU cores provisioned to the runtime. Typically that is
the number of CPU cores in a physical machine of number of virtual cores assigned to a VM.
So if the VM is assigned 2 virtual cores then it would require 2 Anypoint vCores.”

Factors That Impact Mule Sizing

MuleSoft Sizing Overview
34

Sizing Factors
● The number of APIs to deploy

Sizing Factors
● Peak volume or number of transactions per unit of time

Sizing Factors
● Payload size

Sizing Factors
● Payload size
● Business logic complexity

Sizing Factors
● Payload size
● SLA and backend latency

Sizing Factors
● Payload size
● Integration patterns

Sizing Factors
● Payload size
● Deployment Model

Sizing Factors
● Payload size
● Deployment Model
● Number of production and non-production environments in use

Volume
Transactions Per Second
or TPS
Number of Transactions / Unit of Time

Payload Size
Payload size in KB

Payload size is inversely proportional to TPS
Deployment
conﬁg
CloudHub 1 vcore worker
Managed API with embedded
Gateway
API detail
APIkit Router with OAS 2.0
GET /orders
application/json
Request
header
~500b (including 400b of JWT
token)
Protocol Plain HTTP
Backend
latency
50ms
SLA 500ms Strict (99% line)
Complexity Simple
Impact of Varying Payload Size
Sizing factors
45

Business Logic Complexity
SIMPLE
MEDIUM
COMPLEX

SLA and Backend Latency
Service Level Agreements
(usually measured in ms)

SLA is inversely proportional to vCores
Impact of Varying SLA on Sizing
API detail
APIkit Router with OAS 2.0
GET /orders
application/json
Request header
~500b (including 400b of JWT
token)
Protocol Plain HTTP
Backend latency 50ms
Response
payload
100kb JSON
Expected TPS 700+
Complexity Simple
48

Integration Patterns
49
Batch vs Real Time

Sizing Nuances in Cloudhub vs
OnPrem vs Runtime Fabric

Click-and-conﬁgure scale up/out from Runtime Manager
CloudHub Deployment
DNS,
LBR
AWS
Region
SCALE
UP
SCALE
OUT
51

Should you size for peak or average throughput?
CloudHub bursting and impact on sizing for peak
52

Sizing Nuances for On Premise Mule Servers
● 1 core per instance
● 2 cores are recommended
● 25 max lightweight applications per
core

Considerations
Anypoint Runtime Fabric Sizing

Limitations
Anypoint Runtime Fabric Sizing
Maximum Controller Nodes: 5
Maximum Worker Nodes: 16
Maximum Replicas Per Worker Node: 40
Maximum # of Environments per Runtime
Fabric: 50
Maximum # of Runtime Fabric Instances In a
Business Group: 50

Runtime Fabric Sizing Example
Example: Anypoint Platform Base subscription customer is licensed for 2 cores of Mule in
production. The RTF deployment would be:
● 2 worker nodes with 2 cores each
● Each worker node has approx 0.5 cores reserved for internal services, leaving ~1.5 vCPU per worker node
○ Total of 4 cores (2 nodes x 2 cores each) minus ~1.0 core (2 nodes x 0.5cores each) = ~3 vCPU
● With Runtime Fabric v1.6, customers could deploy up to 20 simple applications (thumb rule) per CPU core on
Runtime Fabric
○ Reserving 0.02 vCPU & Limiting (bursting) 2.0 vCPU or higher
● With 2 worker nodes, there are approx 3 vCPU used to deploy Mule apps. However, each worker node only has
~1.5 vCPU available, so that’s the most an application can burst up to.
● Note: The total available vCPU is 3, so customers must look at their applications CPU utilization to ensure, in
aggregate, no more than 2 cores are used at any given time
56

<< TOC
T-shirt Sizing

T-shirt Sizing
59
𝚺(number of apps under each
t-shirt size x recommended core
size of the t-shirt)

T-shirt Sizing: Approach
Size Criteria Cores
Small
5-30 TPS, Payload size upto 100kb, Simple Logic
or File size under 1GB
0.1
Medium
30-100 TPS, Payload size upto 100kb, Medium
Logic or File size 1-2GB
0.2
Large
100-400 TPS, Payload size 100kb - 200kb,
Medium to Complex Logic or File Size of 2–4GB
1
X-Large
400 or above TPS, Payload size 200kb or more,
Complex Logic or File size 4GB or above
2
Other factors taken into
consideration are:
● Sync vs async
● Real time vs batch
● Strict SLA requirements
● Payload size variations
● API-led Architecture
● High Availability
Run your own performance
benchmarks - The actual
capacity may vary 30-60% when
all the factors are combined
60
Capture a ballpark estimate based on the most basic factors:
TPS, Payload Size & Logic

High Availability

What is High Availability?
62

When to use High Availability
CloudHub provides 99.99% (aka ‘four nines’) availability as standard. In principle, this allows 52
minutes and 36 seconds of downtime per year.
The SLA provided by on-premise options depends on the customer’s infrastructure.
● If the business can tolerate a service going down for this long, and coming back later, they
probably don’t need HA.
● If the business requires better service, or entirely uninterrupted service, they need HA.
Things to remember about HA:
● High availability requires protection end-to-end. There is little point having a highly-available
MuleSoft API, if the underlying system or network is unreliable.
63

Up to 100 TPS
HA: no
either
100-200 TPS
HA: no
either
200-300 TPS
HA: no
or
Up to 100 TPS
HA: yes
or
Up to 200 TPS
HA: yes
Horizontal Scaling
Mule app
Mule app Mule app
LB
Mule app Mule app
LB
Mule app
A B C
64

HA - Simple sizing
HA = 2x cores
Sizing for high availability (HA)
Drivers and Approach
HA - Detailed sizing/high volume
Consider
● which APIs need HA?
● is a reduced service level acceptable
during an HA recovery?
● Do you need to double cores, or is adding
a worker suﬃcient?
65

Questions?

Thank you!

MuleSoft Sizing Guidelines - VirtualMuleys

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a MuleSoft Sizing Guidelines - VirtualMuleys

Similar a MuleSoft Sizing Guidelines - VirtualMuleys (20)

Más de Angel Alberici

Más de Angel Alberici (11)

Último

Último (20)

MuleSoft Sizing Guidelines - VirtualMuleys