Cloudhub updates an app with zero down time

Describing the out of box feature provided by Cloudhub to update an application with zero down time

Transcript

1. Cloud hub provides zero downtime Author : Arun V S
2. Cloud hub provides zero downtime  Key takeaway from this walk through:  Upgrade a Mule Application running on the Cloudhub and understand that the application updates with zero down-time
3. Scenario  Initally you have configured the worker size as 0.1 vCores. For some reasons if you want to update by increase the worker size as 0.2 vCores.  By doing this so, it will lead to some downtime. i.e, to undeploy the old application and deploy the application with new worker as worker size is changed.
4. Updating Worker Size in Clouhub(here)
5. Cloudhub's Out of Box Feature  While increasing the worker size, behind the scenes, Cloudhub provides this out of box feature that makes our old worker with 0.1 vCore that holds the old application is still running until a new worker with 0.2 vCore is created with the same application.  In cloudhub, when you change the vCore size, the application status will be changed to "Updating". While the status is updating, whatever the request that are sent by the user are sent to the old worker with 0.1 vCore.  When the application status is changed to "Started", it is clearly understood that worker with 0.1vCore is stopped completely. Here after, the new requests will route to the worker with 0.2 vCores. Cloudhub's this out of box feature provides zero downtime for updating an application.