20/08/2024 Migration from CH 1.0 to CH 2.0 INDY MuleSoft Meetup Group
Why Cloud Hub 2.0 Shared Space vs. Private Space Cloud Hub 2.0 Deployment Cloud Hub 2.0 Architecture Cloud Hub 1.0 and 2.0 Feature Comparision Live Demo of Migration From CH 1.0 to CH 2.0 Q & A Agenda ‹#›
Introduction
Integration Lead at Salesforce Inc,USA MuleSoft Meetup Leader Mulesoft Certified Integration Architect 18 years of Experience in Software development and Design https://www.linkedin.com/ in/ikram-mohamed-b4515115/ ‹#› Ikram Mohamed Organizer Your Photo
Technology Architect at Infosys MuleSoft Ambassador MuleSoft Meetup Leader Mulesoft Certified Integration Architect 13 years of Experience in Integration Domain https://www.linkedin.com/in/vikas-sharma-50b391a5/ https://www.youtube.com/@YourIntegrationBuddy ‹#› Vikas Sharma Speaker Your Photo
CloudHub 2.0
Why CloudHub 2.0 ‹#› Orchestration Services Deploy and run applications in containerized environment based on EKS Provides a standardized isolation boundary by running each Mule instance and service as a separate container Provides for deployments across 12 regions globally. Dynamic Scalable. Horizontal Scaling can be easily achieved by increasing number of replica and Vertical Scaling can be easily achieved by increasing vCores size. More granular vCores option. Maximum vCores can be allocated to per replica is 4 vCores. Application can be deployed on Clustered mode. Minimum 2 replicas required for Clustering. Supports features like Intelligent Healing, Zero-Downtime updates etc. Support for the Rolling update and Recreate while application deployment.
Why CloudHub 2.0 Contd.. ‹#› Anypoint Control Pane Anypoint Monitoring & Logs Object Store V2 Runtime Manager Anypoint Exchange Access Management MuleSoft Platform Services 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 Fully managed by MuleSoft Lightweight containerization Granular resource allocation Enhanced security CloudHub 2.0 features and its comparison with CloudHub 1.0 and RTF
Shared Space CloudHub 2.0 Shared and Private Space ‹#› Private Space A shared space is an elastic cloud of resources that includes Mule instances running in a multi-tenant environment You don’t require isolation from the public cloud. Your apps don’t need to connect to an on-premises data center Your apps can use the cloudhub.io domain name ( rather than a vanity domain name) You don’t need to configure custom certificates A private space is a virtual, private, and isolated logical space in CloudHub 2.0 in which to run your apps A private network , which is a virtual cloud where apps deployed to this private space run. 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. 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.
Shared Space ‹#› Orchestration Services Private Space
Deployment Model CloudHub 2.0 Deployment Rolling update Maintain older version before your application is redeployed Extra vCores needed Recreate Terminate old replica Deploy new replica Quicker then Rolling Update No-extra vCores needed ‹#› Replica Size (0.1, 0.2, 0.5 vCores etc.) Number of replicas (1 to 8) Sizing