Less than a year ago we announced the availability of the first vFabric Application Director release, where we took a bold new approach to provision workloads on Cloud Infrastructure. It was an inventive solution to a problem most people hadn’t realized was an issue yet. By separating apps and infrastructure in the provisioning process, we could drastically simplify operations and actually make organizations more nimble, more agile.
This week, we announced the next major release of Application Director. Over the course of the past year, we have seen tremendous responses from our design partners, early adopters and overall in the market to the approach we are delivering. Komal Mangtani, our engineering director who is building Application Director, first outlined this approach in her post ‘Creating Your Self-Curating Application Platform’ back in August. Essentially, we are using a completely declarative, model-driven method for service provisioning, which means it is agnostic of the underlying configuration script or the infrastructure it is running on.
Automation for any process is expected to speed things up, and reduce errors. By abstracting this into the model-driven approach, we get a few more benefits: