Anypoint Platform CloudHub 2.0

“As we all know Cloudhub 2.0 is a new way of deploying API’s, where it is full managed, containerized cloud service”

Reasons to Deploy on CloudHub!

• Dynamically scales infrastructure and built-in services up or down.
• Builds in security policies, protecting your services and sensitive data with encrypted secrets, firewall controls, and restricted shell access.

CloudHub 2.0 improvements make it easier to learn, develop, and manage than CloudHub 1.0. Benefits include:

• Seamless Mule clustering for deployments with more than one replica.
• Container-based application deployment to regulate resource consumption, ensure application availability, and enable scalability.
• Deploying applications to shared spaces, which do not require advanced setup or infrastructure maintenance.
• In CloudHub 2.0, private spaces function as improved VPCs from CloudHub 1.0. You can automatically assign a private network for the applications in a private space. You can also configure a private ingress load balancer that auto-scales to accommodate traffic.
• Applications now have public and private endpoints by default. You can also configure multiple public endpoints. You can access the endpoint addresses in Runtime Manager.
• 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.
• Using ports 80 and 443, applications inside a private space can communicate using internal load balancer via the private endpoint. Note that this depends on application protocol.

Don't we have any Limitations/Considerations!! we do have few

Infrastructure Considerations:

• To move applications between regions, you must redeploy the application to another shared space or private space in a different region. You cannot move the app to a different region once deployed.
• CloudHub 1.0 VPC peering and direct connect have been deprecated in CloudHub 2.0. You can now use transit gateway attachments. Further, when you delete a private space that has a transit gateway attached, the transit gateway is preserved, and you can reattach it to a different private space.
• CloudHub 2.0 does not support the following infrastructure features or functions that CloudHub 1.0 supports: Anypoint Security, Secrets Manager, Tokenizer.

Application Considerations:

• Only Mule 4.3.0 through 4.4.x are supported.
• Application bursting depends on the resource usage of other applications that are deployed in the private space and is not guaranteed.
• Use Anypoint MQ for persistent queues and other queue management. Persistent queues are not supported.
• CloudHub 2.0 does not support the following application features or functions that CloudHub 1.0 supports:

1. Mule versions prior to 4.3.0
2. Overwriting JVM parameters

3. Overriding default JVM truststores with custom truststores

4. Configuring application ingress path rewrite rules

5. Using log points in Anypoint Monitoring

6. Creating custom notifications

7. Using the CloudHub Connector.

CloudHub 2.0 imposes the following limits:

Private spaces per organization: 100

VPNs per private space: 10

Transit gateway connections: 5, depending on available network connection entitlements

Custom TLS contexts per private space: 10

Firewall rules (inbound): 40

Firewall rules (outbound): 40

Application size: upto 200 mb