Pre Engineered Building Manufacturers Hyderabad.pptx
Melbourne Virtual MuleSoft Meetup December 2022
1. Melbourne Virtual MuleSoft Meetup
CloudHub 2.0
8th December 2022
Feel free to ask questions in the chat
We will commence at 17:30 AEDT
2. 2
Use the chat function to ask questions and comment.
We will use Quizizz for our trivia later in the meetup.
Welcome to the Meetup
3. 3
Meet your local Meetup leaders
Join the group at meetups.mulesoft.com/melbourne
to be notified of all future events
Daniel Soffner
MuleSoft
Strategic Technical Architect
Adam Bond
MuleSoft
Principal Solution Engineer
Carlos Rodriguez Iturria
MuleSoft
Global Partner Engineer
5. 5
Your Agenda for today
★ Welcome and Updates (Adam Bond, MuleSoft)
★ CloudHub 2.0 (Daniel Soffner and Tim Dai, MuleSoft)
★ Trivia and Giveaways (Daniel Soffner, MuleSoft)
22. Private Space - Private Kubernetes Cluster
Replica - Container instance of an API
Ingress Controller
CloudHub 2.0 Features
VPC - Virtual Private Cloud
Worker - EC2 server instance of an API
DLB - Dedicated Load Balancer
Terminology Changes
23. Replicas
CloudHub 2.0 Features
Dedicated instances of Mule runtime engine that run your integration applications on
CloudHub 2.0
Similar to the concept of CloudHub 1.0 workers
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.
24. CloudHub 2.0 Features
Replicas - Capacity
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)
● Bursting depends on other applications
deployed in the shared/private space
Replicas with 1 or more 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
25. Shared Global Regions
CloudHub 2.0 Features
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 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 a value for shard
■ For apps deployed to shared spaces, each region might have multiple Shard values
The load balancer that CloudHub 2.0 uses to route requests resides in the same region as
your application.
26. Availability & Scalability
CloudHub 2.0 Features
Availability
● Redundant platform: All CloudHub 2.0 platform services have at least one built-in layer
of redundancy and are available in at least two data centers at all times.
● Intelligent Healing: CloudHub 2.0 monitors the replicas for problems and provides a
self-healing mechanism to recover from them.
○ If the underlying hardware experiences a failure, the platform migrates your application to a
new replica automatically
○ In the case of an application crash, the platform recognizes the crash and can redeploy the
replica automatically.
● Zero-Downtime Updates: CloudHub 2.0 supports updating your applications at runtime
so end users of your HTTP APIs experience zero downtime.
27. Clustering
● Provides scalability, workload distribution, and added reliability to applications on
CloudHub 2.0
● Horizontal Scalability: With clustering you can add multiple replicas to your application
to make it scale horizontally
○ CloudHub will automatically distributes replicas of the same application across two or more
data centers for maximum availability
○ HTTP load balancing automatically distributes requests across these replicas in a round robin
fashion
Autoscaling (Coming Soon)
● Application auto-scaling feature is available to all customers but the features will be
available to all customers once the new consumption based pricing launches
Availability & Scalability
CloudHub 2.0 Features
28. Application Monitoring and Automatic Restarts
CloudHub 2.0 Features
CloudHub 2.0 monitors all applications and restarts them automatically if necessary so that
your applications recover without your intervention.
CloudHub 2.0 displays a notification that the app is restarting and another to report the
success or failure of the restart.
The logs report the details of the restart procedure.
● You can also receive alerts and diagnostic information if your application becomes
unresponsive.
29. Security
CloudHub 2.0 Features
CloudHub 2.0 does not inspect, store, or otherwise interact directly with payload data
CloudHub 2.0 collects monitoring, analytics, and log data from CloudHub replicas and might
perform actions on behalf of the user
● All communication between platform services and CloudHub is secured using SSL with
client certificate authentication
Application property values can securely be stored in a way that is not viewable or retrievable
by any user
31. 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
32. 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
33. Private Spaces
CloudHub 2.0 Architecture
In each private space, you define:
● A private network, which is a virtual cloud where apps deployed to this private space run.
○ Private space name
○ Private network region
○ CIDR Block
○ Connection Type
■ VPN
■ Transit Gateway
○ Internal DNS Servers (Optional)
● One or more connections from the private network to your external network, either via
Anypoint VPN or a transit gateway
● TLS contexts, which define the domains that are available when deploying apps to the
private spaces, and optionally enable mutual TLS.
● 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.
34. Patching
CloudHub 2.0 Architecture
Operating system patching
● CloudHub 2.0 manages the operating system patching
● Will occur monthly
● Patch updates use blue-green deployment, which ensures zero downtime.
Mule runtime patches
● Mule Runtime patching will be executed ad-hoc in a different schedule than CloudHub
1.0 for the near term future, initially it will only be for major security issues
● As CloudHub 2.0 adoption increases, the patching scope and schedule will converge to
the CH 1.0 current process
35. CloudHub 2.0 - Private Space
Internal & External APIs
RUNTIME
MANAGER
ACCESS
MANAGEMENT
MANAGEMENT
CENTER
VISUALIZER
ADVANCE
MONITORING
EXCHANGE
PARTNER
MANAGER`
API DESIGNER
DESIGN
CENTER
API
ANALYTICS
Data
Plane
Anypoint Runtime
Anypoint Platform
INFRASTRUCTURE
PROVISIONER
Worker Worker
Mule
App
Mule
App
Mule
App
Mule
App
Worker
Mule
App
Mule
App
Runtime Fabric services
Docker & Kubernetes (nodes)
EKS Management Plane
Anypoint Runtime Fabric
Worker Worker
Mule
App
Mule
App
Mule
App
Mule
App
Worker
Mule
App
Mule
App
Runtime Fabric services
Docker & Kubernetes (nodes)
EKS Management Plane
Anypoint Runtime Fabric
N Number of
Anypoint Runtime Fabric
Private Space Private Space Private Space
Control Plane
Region
Business Group
*
40. General Limitations
CloudHub 2.0 Limitations
Runtime Support
● 4.3.0 - 4.4.x are supported
Unsupported
● Anypoint Security
● Secrets Manager
● Tokenizer
● WAF Policies
● API Proxies (Coming Soon)
40
41. Bursting
CloudHub 2.0 Limitations
Previously in CH 1.0, users had AWS CPU credits available which were possible to be
optimized around
● In CH 2.0 every application will have bursting configured by default but won’t be as
predictable as CH 1.0
● Bursting capabilities will be dependent on other applications running in the same
shared/private spaces
Workarounds have been identified for customers relying on predictable bursting
● Create a dedicated private space
● Schedule jobs so only one runs at a time
41
42. VPCs/Spaces
CloudHub 2.0 Limitations
Private Spaces are the evolution of VPCs in CloudHub 1.0
TLS 1.0/1.1 will not be supported
● TLS 1.3 is supported
Only VPN and Transit Gateway will be supported
● VPC Peering and Direct Connect will be deprecated
42
43. Applications
CloudHub 2.0 Limitations
Application names are only required to be unique at the Private Space/ Organization /
Environment level
● In CH 1.0 applications were required to be globally unique per region
Restarts of applications require stops/starts as opposed to restarts in CH1
Auto-scaling is not available yet
● Will be available come with the new consumption based pricing release
Two different deployment modes for patching
● Rolling: Spin up a new version of the application in parallel and scale down the old
version once successful. Ensures zero downtime
● Recreate: Existing version will be shut down before the new version is deployed. Used
when multiple versions cannot be deployed simultaneously
43
44. Static IPs
CloudHub 2.0 Limitations
2 to 3 Inbound and Outbound Static IPs are automatically provisioned per Private Space
● The inbound static IPs are attached to Network Load Balancers proxying the K8S Ingress
resource
● The outbound static IPs are attached to NAT Gateway
● The Static IPs do not get deducted from the customer subscription, they are offered in
addition to what they have
Every deployed application in the same Private Space will use the same set of Inbound and
Outbound static IPs
44
45. Alerts
CloudHub 2.0 Limitations
In Runtime Manager, deployment success and deployment failure are the only 2 supported
alert definitions.
● Additional alerting will now need to be set up via Anypoint Monitoring
CloudHub Connector / Custom alert notifications (Bell icon) are no longer supported
Log Points are currently not supported in CloudHub 2.0
● This functionality is on the roadmap
45
47. Trivia
There are prizes to be won
Open joinmyquiz.com on your mobile phone browser
Login with the Game PIN we will give you in a minute
Use your real name to win prizes