Anypoint cloudhub 2.0

1. Patna MuleSoft Meetup Group
Anypoint Cloudhub 2.0
7th Jan 2023

2. Organizers
A SHOW OF HANDS:
Who is new to this Meetup?

3. Safe Harbour Statement
● Both the speaker and the host are organizing this meet-up in individual capacity only. We are
not representing our companies here.
● This presentation is strictly for learning purposes only. Organizer/Presenter do not hold any
responsibility that same solution will work for your business requirements.
● This presentation is not meant for any promotional activities.
3

4. A recording of this meetup will be uploaded to events page within 24 hours.
Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab.
Make it more Interactive!!!
Give us feedback! Rate this meetup session by filling feedback form at the end of the day.
We Love Feedbacks!!! Its Bread & Butter for Meetup.
Housekeeping
4

5. ✔ 17+ years of Total Experience.
✔ 5+ years of experience in MuleSoft
✔ Working as Senior Integration Architect & Project Manager at TCS
✔ MuleSoft certified Delivery Champion
✔ MuleSoft Mentor and active in MuleSoft Community
✔ Certified MuleSoft Developer & Architect
● About the Speaker
Ananda Sankar Joardar
Tata Consultancy Services
Integration Architect
Speaker
5

6. 6
Introduction
What is CloudHub 2.0
Features
Architecture
Multi-Tenancy
Availability & Scalability
Last Mile Security
CloudHub 2.0 – Deployment Flow
CloudHub 2.0 – Application Monitoring
Agenda

7. What is CloudHub 2.0
7
★ Containerized iPaaS offerings
★ Fully managed by MuleSoft
★ Deployment of MuleSoft Application on lightweight container
★ Isolation of applications

8. 8
Virtual Machine Vs Containers
Hypervisor
Infrastructure
APP A
Bin/Lib
Guest OS
APP B
Bin/Lib
Guest OS
Container Engine
Host Operating System
Infrastructure
APP A
Bin/Lib
APP B
Bin/Lib
Virtual Machine Virtual Machine
Container Container
Virtual Machine – CloudHub 1.0 Container– CloudHub 2.0

9. Features

10. Key highlights
10
Container-based - Faster spin up of application
vCore allocation - more granularity than earlier
Outbound Firewall rule configuration - egress traffic
Application clustering on more than one replica
Shared Space – zero infrastructure maintenance

11. Where CloudHub 2.0 Precedes over
CloudHub 1.0
Newly added fractional vCore – better resource optimization
Auto scaling of private Ingress load balancer
VPN high availability is out of the box
Private space Apps have both public and private endpoints
Configuring multiple Public endpoints is also possible -private space
Log enable/disable feature is out of the box
No need of globally unique Name - append unique id automatically -
testapp-uniq-id.shard.usa-e1.cloudhub.io.

12. Key Considerations to deploy on CloudHub 2.0
Does not support Direct Connect and VPC Peering - Transit Gateway
and VPN is available
Applications if not running but deployed still consume vCore licenses -
Delete the application to free up vCore
Redeployment is the only option to move applications between regions
Private space can be associated with multiple environments based on
the type of the environment (Sandbox or Production type Environment)
and Business Groups
CloudHub 2.0 only supports Mule 4.3.0 to 4.4.x

13. Features not supported in CloudHub 2.0
Anypoint Security Overwriting JVM parameters
Secret Manager Overriding default JVM truststores with custom
truststores
Tokenizer Log points in Anypoint Monitoring
Web Application Firewall Policies Custom Notification creation and Cloudhub
connector
Get From Sandbox feature TLS 1.0
Insights DataGraph
Mule Runtime versions prior to 4.3.0
*** Features are Keep on getting Updated– Please check before decide on CloudHub 2.0

14. Architecture

15. CloudHub 2.0 – Architecture
15

16. 16
★ Each Replica has a specific amount of capacity (CPU and Memory)
★ Each Replica runs in a separate container that ensure isolation from other
applications
★ Each Replica is deployed and managed independently
★ Each Replica runs in a specific global region like US, EU or APAC
★ Each Replica has a minimum of 8 GB of storage for both system and
application. To increase the storage capacity, add 2 or more workers
★ If applications need more vCore than what is available , CloudHub 2.0 still
allows the deployment, but applications can not be started to use until
additional vCore is added.
★ The metaspace limit of applications deployed to CloudHub 2.0 is currently
256 MB. Threshold limit for GC for metaspace is at 128 MB
CloudHub 2.0 - Replicas

17. CloudHub 2.0 - Multi-Tenancy
17
★ Shared Global Space—Co-tenancy without having access to applications and data of
another tenant
★ Single Tenant Private Space—Virtual and isolated space in CloudHub 2.0 for deployment
★ Management Console and Platform services—control plane is shared by all tenants.

18. 18
 Redundant Platform—All CloudHub 2.0 platform services (from load
balancing to the API layer) are supported with at-least one built-in layer of
redundancy. Services are deployed on at least two data center more than 60
miles apart
 Intelligent Healing—CloudHub 2.0 monitor replicas and apply a self healing
mechanism to recover from any problem.
 CloudHub 2.0 Zero Downtime Upgrade
 Clustering—This feature provides scalability, workload distribution and
added reliability to applications
CloudHub 2.0 Availability & Scalability

19. CloudHub 2.0 – Last Mile Security
19

20. CloudHub 2.0 Deployment

21. CloudHub 2.0 – Deployment Flow
21
Designer Studio
Exchange
Anypoint CLI
API
Runtime
Manager
Container
Retrieve Artifacts
Mule Maven
Plug In

22. CloudHub 2.0 Monitoring

23. CloudHub 2.0 Application Monitoring
23
Dashboard Logs
Diagnostics Alerts
o More than 80 in-built Metrics
o Covers – Inbound, Outbound, JVM,
Performance, Failure & Infrastructure
o Custom Metrics for trends and
comparative analysis
o 100 MB per application or 30 days by default
o Filter based on Configuration, Replica, Log
Level, Time
o Search with specific criteria or by Correlation
ID
o Snapshot of all threads in a
replica
o Latest status on the top
o Thread dump shows current
server status
o Alerts for application or server
event
o Trigger Notifications

24. Demo

25. Q&A

26. Take a stand !
26
●Nominate yourself for the next meetup speaker and suggest a topic as well.

27. 27
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: https://meetups.mulesoft.com/patna/
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
○ Reach out to Patna Meetup Leaders (Om/Amit/Shyam) to suggest topics for next Meetup
What’s next?

28. Thank you