The determining factor for cloud service performance is not the number of deployed cloud instances, it is the number of cloud instances that are fully operational (active and doing what they are supposed to) at any given time. Using the elastisys cloud platform, it is easy to keep the number of operational cloud instances at a given level, and thereby ensuring good performance. Cloud instances that stop being operational are detected when they fail one of the ongoing continuous health checks. Cruise control ensures that they are isolated from the others, and your operations team is alerted. That way, they can immediately start tracking down the root cause of the incident. But until that happens, your cloud deployment should never have to suffer from incorrect capacity allocation: to make up for the isolated cloud instance, Cruise control starts a new instance to replace the old one and makes it part of the cloud pool.
Using the elastisys cloud platform’s cruise control features is simple: provide it with your cloud credentials, enable monitoring, and define what constitutes a failure to provide your service. Once that event occurs, the affected cloud instance will be isolated and replaced, but not stopped or otherwise destroyed, since investigating it will offer your operations team great insight in how to avoid future similar events.
Elastisys cloud platform does cruise control right. With it, unforeseen errors do not degrade service performance beyond an immediate cloud instance restart, and your operations team can easily investigate the root cause for any issue. It just works.