Moving to the Cloud is a real challenge - especially when it involves migrating your existing applications.
While you want to maximize the benefits of cloud integration, such as consuming resources according to business demand and automating processes to gain agility; you don't want to change your application or choice of stack, or lose control.
Cloudify’s DevOps approach treats infrastructure as code, enabling you to describe deployment and post–deployment steps – for any application – through an external blueprint – AKA , a recipe.
Once the recipe is created…
To move your application to the cloud, you don’t have to commit to any particular cloud or middleware vendors, or even OS distribution. It’s not just about technical preferences – it’s about costs and business decisions. You simply can’t afford to get locked–in.
That’s why Cloudify hides the APIs and cloud configuration from your application and recipe, so your investment in Cloudify recipes can be taken from one cloud to another, unchanged.
Cloudify's cloud driver configurations enable you to create as many resource templates as required.
Cloudify makes your application highly–portable, and on the other hand it enables you to fine–tune your deployment, maximizing the benefits you can gain from the cloud.
A cloud driver configuration specifies the images, hardware, networking, and security protocols you want the cloud to use with each of your application services.
Cloudify applies the DevOps principle across the board, describing every aspect of your production environment as code or configuration.
For example, Cloudify codifies where and how to get your middleware binaries, dynamic configurations, and the rules for monitoring and scaling. What’s more, these files can be changed and audited as required.
DevOps means your infrastructure is treated like code, so it is fully automated, yet maintainable and auditable.
Rule of thumb – if you can script it, you can make it happen with Cloudify.
