Speaker: Anu Vijayamohan Host: Angel Alberici VirtualMuleys: 66 - 20220304-April Recording & Slides: https://meetups.mulesoft.com/events/details/mulesoft-online-group-english-presents-mulesoft-sizing-guidelines/ All Recordings & Slides: meetups.mulesoft.com/online-group-english/ & youtube.com/c/VirtualMuleysOnline/videos In this session we will discuss: Core concepts of sizing Factors that impact mule sizing T-Shirt sizing Sizing nuances in Cloudhub vs OnPrem vs RTF High Availability

1. 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

2. All contents © MuleSoft, LLC
Virtual Muleys Meetup
(Online Group - English )
Moderator: Angel Alberici
Meetup Edition, 2022
Recording
66

3. All contents © MuleSoft, LLC
Virtual Muleys Meetup (Online Group - English)
9
9

4. All contents © MuleSoft, LLC
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!

5. All contents © MuleSoft, LLC
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

6. All contents © MuleSoft, LLC
● 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?

7. All contents © MuleSoft, LLC
[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

8. All contents © MuleSoft, LLC
[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/

9. All contents © MuleSoft, LLC
[March 21st Release] Anypoint DataGraph Release Notes
18
https://docs.mulesoft.com/release-notes/datagraph/anypoint-datagraph-release-notes#march-21-2022

10. All contents © MuleSoft, LLC
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
configuration files
● 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

11. All contents © MuleSoft, LLC
https://www.mulesoft.com/lp/reports/connectivity-benchmark
MuleSoft Benchmark 2022 Report is now available!

12. All contents © MuleSoft, LLC
MuleSoft Sizing Guidelines
Anu Vijayamohan
Customer Success Technical Architect, EMEA

13. All contents © MuleSoft, LLC
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

14. All contents © MuleSoft, LLC
Core Concepts of Sizing

15. All contents © MuleSoft, LLC
What is a Mule Application?

16. All contents © MuleSoft, LLC
What is a Flow?
Mule Flow
25

17. All contents © MuleSoft, LLC
What is a Transaction?
26

18. All contents © MuleSoft, LLC
Deployment: On-Premise
27
Standalone Mule Install
Server
App App
Mule
App
Control plane
YOUR NETWORK

19. All contents © MuleSoft, LLC
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

20. All contents © MuleSoft, LLC
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

21. All contents © MuleSoft, LLC
Monolith
Mule Runtime (Ex 1 core)
Account Salesforce API Account SAP API Account Billing DB API
30
Runtime Considerations

22. All contents © MuleSoft, LLC
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

23. All contents © MuleSoft, LLC
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.”

24. All contents © MuleSoft, LLC
Factors That Impact Mule Sizing

25. All contents © MuleSoft, LLC
MuleSoft Sizing Overview
34

26. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy

27. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy
● Peak volume or number of transactions per unit of time

28. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy
● Peak volume or number of transactions per unit of time
● Payload size

29. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy
● Peak volume or number of transactions per unit of time
● Payload size
● Business logic complexity

30. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy
● Peak volume or number of transactions per unit of time
● Payload size
● Business logic complexity
● SLA and backend latency

31. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy
● Peak volume or number of transactions per unit of time
● Payload size
● Business logic complexity
● SLA and backend latency
● Integration patterns

32. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy
● Peak volume or number of transactions per unit of time
● Payload size
● Business logic complexity
● SLA and backend latency
● Integration patterns
● Deployment Model

33. All contents © MuleSoft, LLC
Sizing Factors
● The number of APIs to deploy
● Peak volume or number of transactions per unit of time
● Payload size
● Business logic complexity
● SLA and backend latency
● Integration patterns
● Deployment Model
● Number of production and non-production environments in use

34. All contents © MuleSoft, LLC
Volume
Transactions Per Second
or TPS
Number of Transactions / Unit of Time

35. All contents © MuleSoft, LLC
Payload Size
Payload size in KB

36. All contents © MuleSoft, LLC
Payload size is inversely proportional to TPS
Deployment
config
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

37. All contents © MuleSoft, LLC
Business Logic Complexity
SIMPLE
MEDIUM
COMPLEX

38. All contents © MuleSoft, LLC
SLA and Backend Latency
Service Level Agreements
(usually measured in ms)

39. All contents © MuleSoft, LLC
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

40. All contents © MuleSoft, LLC
Integration Patterns
49
Batch vs Real Time

41. All contents © MuleSoft, LLC
Sizing Nuances in Cloudhub vs
OnPrem vs Runtime Fabric

42. All contents © MuleSoft, LLC
Click-and-configure scale up/out from Runtime Manager
CloudHub Deployment
DNS,
LBR
AWS
Region
SCALE
UP
SCALE
OUT
51

43. All contents © MuleSoft, LLC
Should you size for peak or average throughput?
CloudHub bursting and impact on sizing for peak
52

44. All contents © MuleSoft, LLC
Sizing Nuances for On Premise Mule Servers
● 1 core per instance
● 2 cores are recommended
● 25 max lightweight applications per
core

45. All contents © MuleSoft, LLC
Considerations
Anypoint Runtime Fabric Sizing

46. All contents © MuleSoft, LLC
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

47. All contents © MuleSoft, LLC
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

48. All contents © MuleSoft, LLC
<< TOC
T-shirt Sizing

49. All contents © MuleSoft, LLC
T-shirt Sizing
59
𝚺(number of apps under each
t-shirt size x recommended core
size of the t-shirt)

50. All contents © MuleSoft, LLC
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

51. All contents © MuleSoft, LLC
High Availability

52. All contents © MuleSoft, LLC
What is High Availability?
62

53. All contents © MuleSoft, LLC
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

54. All contents © MuleSoft, LLC
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

55. All contents © MuleSoft, LLC
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 sufficient?
65

56. All contents © MuleSoft, LLC
Questions?

57. All contents © MuleSoft, LLC
Thank you!