Make Continuous Delivery Easy with Model-Driven Releases

by September 28, 2018

New technology is always exciting, and something many of us can’t wait to experiment with. But what happens to our older systems—the ones that have been keeping the lights on all this time—when we rush off with the latest thing? They still power the business, but are often forgotten about. This can be particularly risky when we’re instructed by the top level to immediately implement the latest and greatest tech. So how do you align the two?

If there is disconnect between an overarching strategy and the workers on the ground, teams drift apart and the scale and complexity of any orchestration or management becomes increasingly challenging. This is magnified the more rapidly technology advances and is becoming increasingly prevalent in areas such as cloud migration.

Currently, deployments are often too closely tied to on-premises models and tooling, yet simultaneously the company in question will have a cloud strategy in place and have moved data centers there. This raises the question: how do you adapt for what you have today and bridge the gap for tomorrow? Indeed, a second question replaces the word ‘adapt’ with ‘protect’. In the modern era, security and governance are increasing important, but typically only added into development cycles late in the day. Axiomatically, this results in delays, rework and a lot of risk exposure. These same questions and challenges are popping up throughout the entire enterprise.

The picture is further complicated by the array of apps and services that all work together and are spread across the entire business. Different teams will be all be using different technology stacks and tools across each and every environment. Thus finding a consistent, reliable approach that can account for—and indeed harness—this diversity is crucial for the modern enterprise.

Model-Driven Releases

CA Continuous Delivery solves these problems by using model-driven releases, which enable consistent, repeatable processes regardless of environment. By using a model to define and deliver new functionality, you ensure quality and speed in all environments—including production. This enables teams to ensure their delivery processes are consistent, tested, and proven so that they can be trusted to release whenever needed. By working from a release pipeline and deployment plan, you simplify complexity and standardize the release practice across application stacks.

The model-driven releases within CA Continuous Delivery let you correlate and track the technical improvement to the app(s) that you will make. This part of the model represents both the code and its associated metadata (such as user stories, defects, etc. represented by the specific package). You can also target capacity where the improvements should be deployed, and this can be any mix of on-prem, cloud, PaaS, containers/FaaS, etc. Furthermore, you can establish the automated digital expression of the business rules processes for releasing/deploying improvements.

In addition, CA Continuous Delivery abstracts deployment plans from environments, meaning you aren’t locked into a specific provider and possess the capability to manage releases in hybrid environments—both on-premises and in the cloud. This provides the business with consistency of results despite complexity. Ultimately, CA Continuous Delivery offers a standardized approach with enough flexibility to modeled release pipelines and deployment plans that all application types are supported, across any environment.

The upshot of this approach is that release set-up and design time are drastically reduced, and the business is supplied with a consistency of results despite complexity. All of which means you can take advantage of the latest technology, without sacrificing stability or reliability.