Munich MulesSoft Meetup - Germany 08 Feb 2023

1. Welcome to the Meetup

2. Munich, Germany
CloudHub 2.0
MuleSoft Meetup 08-Feb-2023

3. Introductions

4. Introductions
● Organizers:
○ Chinmay
○ Ganesh
○ Sakthi
● Speaker:
○ Chinmay
4

5. 5
● Both the speakers and the hosts are organizing this meetup in individual capacity
only. We are not representing our companies here.
● This presentation is strictly for learning purposes only.
● Organizers/Presenters do not hold any responsibility that same solution will work for
your business requirements.
● This presentation is not meant for any promotional purposes.
Safe Harbor statement

6. 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!!!
Slow network…No problem. Please disconnect and join back. Troubleshooting in
Bevy virtual https://help.bevylabs.com/article/499-troubleshooting-in-bevy-virtual
Housekeeping
6

7. Agenda
● Important Announcements
● Introduction to CH 2.0
● Key CH 2.0 features
● CH 2.0 Architecture
● Demo
● Q&A
● Feedback
● Networking and Wrap up
7

8. Announcements

9. Announcements - Training
● MuleSoft expert-led training now on Trailhead Academy, effective February 1st.
○ To enroll in a Trailhead Academy Class, you will need to create a TrailblazerID account
○ Browse the training catalog on Trailhead Academy classes page
○ MuleSoft expert-led virtual classes will now be delivered via Zoom
○ MuleSoft Expert-Led Training Experience Guide
● MuleSoft self-paced learning and any scheduled or current MuleSoft certification exam information will
remain available in My Learning accounts on training.mulesoft.com
● MuleSoft Training Credits will be converted to Salesforce Learning Credits, effective February 1st.
○ MuleSoft Training Credits to Salesforce Learning Credits FAQ
○ Salesforce Learning Credits FAQ and Redemption process

10. Announcements - Anypoint Code Builder
● Public Beta for Anypoint Code Builder is now officially available
○ Anypoint Code Builder is MuleSoft’s next-generation IDE (integrated development environment) for
developers to design, develop, and deploy APIs, integrations, and automations from a single
environment.
○ For existing customers: Ensure an Anypoint organization administrator fulfills the prerequisites
listed below. Once completed you can open the Anypoint Platform homepage to find a new Anypoint
Code Builder launch point.
Prerequisites:
Accept the Terms & Condition
Add the permissions to your user role
○ For new developers: Sign up for a free 30-day trial here to get started with the Anypoint Code
Builder (Beta).
● Release Blog post
● Developer Tutorials
● Twitch Stream

11. Intro to CloudHub 2.0

12. Anypoint Control Pane
Anypoint
Monitoring & Logs
Object Store
V2
Runtime
Manager
Anypoint
Exchange
Access
Management
MuleSoft Platform Services
CloudHub 2.0
● Fully managed by
MuleSoft
● Container-based app
isolation
● More granular resource
profile
○ Multi-tenancy
○ Resiliency
○ High availability
○ Platform services
● Enhanced Security
Orchestration Services
Worker Node
Mule App
Monitoring
Mule App
Monitoring
Worker Node
Mule App
Monitoring
Mule App
Monitoring
Worker Node
Mule App
Monitoring
Mule App
Monitoring

13. Private Space - Private Kubernetes Cluster
Replica - Container instance of an API
Ingress
Shared Spaces
CloudHub 2.0 Terminologies
VPC - Virtual Private Cloud
Worker - EC2 server instance of an API
DLB - Dedicated Load Balancer
Public Worker Clouds

14. 14
Get started fast
Set up environments quickly with simplified configuration
for private spaces and network connectivity
Lightweight Isolation
Container based Application isolation
Implement tighter security controls
Built-in security policies that protect services and sensitive
data with encrypted secrets, firewall controls, and
restricted shell access
Low Operational Overhead
Fully managed Cloud Infra. Reduced management
overhead for Load balancing and ingress with new auto-
provisioning and auto-scaling
14
Why CloudHub 2.0?
New

15. 15
Lower Entry point and Cost effective
Granular application resource profiles allow you to start
small and scale up incrementally
Simplified egress controls
Outbound NATing and finer egress firewall control
Accelerate Digital Transformation
With easy setup, simplified configuration and future-proof
architecture helps accelerate growth and innovation faster
15
Why CloudHub 2.0?
New

16. CloudHub 2.0 Features

17. Shared Global Regions
● CloudHub 2.0 provides the ability to deploy apps in four different regions of the world:
○ North America
○ South America
○ European Union
○ Asia-Pacific
● This allows for integrations to be hosted in the location closest to your services
● For an application:
○ The region that the application is deployed to determines the domain provided
○ The load balancer that CloudHub 2.0 uses to route requests resides in the same region
● For the US Cloud and MuleSoft Government Cloud control planes, MuleSoft hosts the management
console and platform services in the United States
● For the EU Cloud control plane, MuleSoft hosts these services in Europe

18. CloudHub 2.0 provides the ability to deploy apps in different regions of the world: North America,
South America, the European Union, and Asia-Pacific.
The region that you deploy your application to determines the domain provided for your
application.
● Myapp-uniq-id.shard.region.cloudhub.io
● CloudHub 2.0 backend service assigned values:
○ Uniq-id: A 6-digit value appended to the app name to ensure uniqueness.
○ Shard: A 6-digit value associated with the space (private or shared) that the app is deployed to.
■ Each private space has a value for shard
■ For apps deployed to shared spaces, each region might have multiple shard values
● Myapp-uniq-id.shard.deu-c1.cloudhub.io - US Control Plane
● Myapp-uniq-id.shard.deu-c1.eu1.cloudhub.io - EU Control Plane
The load balancer that CloudHub 2.0 uses to route requests resides in the same region as your
application.
Region considerations
Runtime Plane
https://docs.mulesoft.com/cloudhub-2/ch2-architecture#regions-and-dns-records

19. Replicas are dedicated instances of Mule runtime engine that run your integration applications on
CloudHub 2.0
Each replica has the following features:
Capacity - Each replica has a specific amount of capacity to process data. Capacity is
determined by the number of vCores assigned to the replica.
Isolation - Each replica runs in a separate container from every other application.
Manageability - Each replica is deployed and monitored independently.
Locality - Each replica runs in a specific global region, such as the US, EU or Asia-Pacific.
Replicas

20. Replicas can be scaled vertically by selecting
one of the available vCores sizes
Replicas with fewer than 1.0 vCores:
● Provide limited CPU and I/O for apps with
smaller workloads
● Can burst to higher CPU speeds for a short
time (unpredictable)
Replicas with 1.0 or higher vCores provide
performance consistency
vCore Size vCPU Heap Memory Total Memory Storage
0.1 0.1 500 MB 1 GB 8 GB
0.2 0.2 1 GB 2 GB 8 GB
0.5 0.5 1.3 GB 2.6 GB 10 GB
1.0 1 2 GB 4 GB 12 GB
1.5 1.5 3 GB 6 GB 24 GB
2.0 2 4 GB 8 GB 40 GB
2.5 2.5 4.75 GB 9.5 GB 50 GB
3.0 3 5.5 GB 11 GB 60 GB
3.5 3.5 6.5 GB 13 GB 70 GB
4.0 4 7.5 GB 15 GB. 88 GB
Replicas
https://docs.mulesoft.com/cloudhub-2/ch2-architecture#cloudhub-2-replicas

21. ● Multi-Tenancy
● High-Availability
● Clustering
● Autoscaling
● App Monitoring and Automatic restarts
● Enhanced Security
Other Features

22. CloudHub 2.0 Architecture

23. CloudHub 2.0 Architecture
Shared Spaces vs Private Spaces
Shared Spaces
● A shared space is an elastic cloud of resources that includes Mule instances running in a
multi-tenant environment.
● CloudHub 2.0 provides one shared space in each supported region.
Private Spaces
● A private space is a virtual, private, and isolated logical space in CloudHub 2.0 in which to run
your apps
● You can create multiple private spaces, either in the same or different regions

24. CloudHub 2.0 Architecture
Shared Spaces vs Private Spaces
Shared Space Private Space
Level of isolation
You don’t require isolation from the public cloud Single-tenancy for your apps is required
Network connectivity
Your apps don’t need to connect to an on-premises
data center
Network connection (VPN or transit gateway
attachment) to a data center required for your apps
Domain names
Your apps can use the cloudhub.io domain name Vanity domain names are required for your apps
Custom certificates
You don’t need to configure custom certificates Custom certificates are required for your apps
Endpoint security
No need for private endpoints Private endpoints are needed

25. CloudHub 2.0 - Private Spaces

26. Private Spaces
CloudHub 2.0 Architecture
In each private space, you can define:
● A private network, which is a virtual cloud where apps deployed to this private space run.
○ Private network region
○ CIDR Block - Sizing is /22 recommended
○ Connection Type (Optional)
■ VPN
■ Transit Gateway
○ Internal DNS Servers (Optional)
● TLS contexts, which define the domains that are available when deploying apps to the private
spaces, and optionally enable mutual TLS. A default TLS Context is provided.
● Firewall rules to allow and block inbound and outbound traffic to your private space.
● The environments and business groups to allow to deploy to the private space

27. Deployment considerations
Ingress
● Customers with private spaces will automatically be provided with a private network for their applications as well as
a private Ingress load balancer
○ This is configured in the Ingress tab
○ The Ingress auto-scales with traffic, removing the concept of DLBs from CH 1.0
■ Thus reducing management overhead of having to configure and manage DLBs
● Ingress logs are available via self-service
● Note: Ingress logs cannot yet be forwarded to a log aggregation server, however it is possible to download
ingress logs from the control plane

28. CloudHub 2.0 - Platform Setup

29. CloudHub 2.0 - Network View

30. Load balancing / Ingress configuration
30
• Applications have Public and Private endpoints.
• Public endpoints are exposed to the public internet
• Inbound non-http based protocols are not supported, only http/https.
• Ingress self-service logs are available in CH 2.0 via Private Space UI
Private endpoints
- Have public DNS entries, but only accessible from within the Private Space/VPNs/Transit Gateway
connections.
- Accessible within the private networks via an internal Ingress (App to App)
- Visible in the Runtime Manager UI

31. CloudHub 2.0 - Private Spaces Ingress

32. Private Spaces - Vanity Domain

33. Demo

34. Q&A

35. 35
● Go to www.menti.com
● Joining Code - 86488109
Feedback

36. 36
● Next Meetup - B2B Integrations with MuleSoft - March 15th
● Share:
○ Tweet your pictures with the hashtag #MuleMeetup
○ Invite your network to join: https://meetups.mulesoft.com/munich/
● Feedback:
○ Contact your organizers
● MeetUp Recordings:
○ Youtube Channel: MuleSoft Meetup Munich
https://www.youtube.com/channel/UCGp3GH-t2NPXG_YSWbnHgjw
● Interested to be a Speaker:
○ Contact your Organizers
● LinkedIn Profile: Mulesoft Munich Meetups
What’s Next

37. 37
● We will now make the Audience as Presenter for the Group picture
● WORD of CAUTION - While leaving the event, Please DONOT click on “End Event
for ALL”. Just close the browser or click on “Leave Event”
Photos and Networking Time

38. Thank you