Cloudhub 2.0


  • CloudHub 2.0 is a fully managed, containerized integration platform as a service (iPaaS) where you can deploy APIs and integrations as lightweight containers in the Cloud
  • It significantly improves application performance and scalability with lightweight container-based isolation and simplified deployment experience to the Cloud

Benefits of Cloudhub 2.0

  • Simplified experience to deploy and run MuleSoft applications in the cloud
  • Every single application can be deployed as a stateless lightweight container which can easily scale up and down
  • Replicas of the same application are deployed across different availability zones providing redundancy and reliability
  • Application can be deployed in just 30 seconds in Cloudhub 2.0
  • The intuitive user interface provides a simplified way to configure VPCs, Load Balancers, and Traffic routing rules all in one place thereby reducing the setup time
  • More granular vCore allocation options
  • In CloudHub 1.0, application names had to be unique, globally, per region. In CloudHub 2.0, the same application name can be used in different deployments in the same private space as long as they are in different environments or organizations
  • You can disable log streaming using Runtime Manager. You no longer need to contact Support to enable or disable this feature
  • The ability to enable the Clustering option and leverage replica scale-out to provide horizontal scalability and reliability to your applications, In CloudHub 1.0, there wasn’t a real concept of clustering
  • Better control of the traffic. In CH1.0, in order to restrict external access to only the External Experience Layer APIs in your customer-owned VPC, it would require setting up two DLBs, in cloudhub 2.0 it is been made simpler by creating a public and private endpoint by default when deploying your application
  • There have been some significant changes in how schedulers are managed in CH2.0. You can now set a specific timezone in the Cron Scheduler, opposite to always using UTC as in CH1.0
  • Every Private space has its load balancer (assigned automatically) for inbound traffic, called Private Ingress


CloudHub 2.0 does not support the following infrastructure features or functions that CloudHub 1.0 supports

  • Anypoint Security and Secrets Manager
  • Persistent VM Queue
  • Tokenizer
  • Creating custom notifications/CloudHub Connector
  • Using the VPC Peering and Direct Connect
Thank you for taking out time to read the above post. Hope you found it useful. In case of any questions, feel free to comment below. Also, if you are keen on knowing about a specific topic, happy to explore your recommendations as well.
For any latest updates or posts on our website, you can follow us on LinkedIn. Look forward to connecting with you there.

Share this:
Notify of
Inline Feedbacks
View all comments