About Automic Continuous Delivery Automation

Automic Continuous Delivery Automation (CDA) is an end-to-end solution for planning, coordinating and automating software release processes, including automated deployments of complex multi-tier applications and configurations across heterogeneous, large-scale server environments.

Watch the video:

Purpose

The purpose of Automic Continuous Delivery Automation is to unify enterprise application and infrastructure automation functionality onto a single platform - without the need of managing multiple tools. Users first architect and control the execution of application process flows, then orchestrate the underlying infrastructure to meet required service levels.

CDA streamlines application release workflow managements for even the most highly-scaled environments while reducing deployment cost across the organization including development, testing, and production.

The goal is to enable consistent, traceable, and auditable deployments for multi-tier applications across heterogeneous and distributed IT infrastructures, reaching from physical or virtual to cloud computing platforms. To improve efficiency, quality and release cycle time, a highly automated system like Automic Continuous Delivery Automation is preferred.

Main Functions

CDA does the following:

Graphic depicting CDA functions

  1. It allows modelling the various components of an application, which are defined as meta-data elements in CDA, with all necessary technical references to the physical elements, and then the packaging of these components for simultaneous deployment. By using the Automation Engine's powerful synchronization capabilities, CDA can deploy, at the same time, the artifacts that are intended to stay together in a single package.
  2. As components of an application generally carry important dependencies across one another, CDA provides native capabilities to build those dependencies via modelling tools, so that the application is deployed in the right sequence. A dependency of a component on another can be enforced using CDA’s modeling tools, rather than makeshift orchestration mechanisms.
  3. CDA deploys the right components to the right environments and it does so natively. Teams no longer have to worry about pushing the proper artifacts to their assigned systems. CDA does that for them.
  4. CDA is capable of staging by allowing users to design structured deployment environments. Hence, each environment like DEV, QA and PRODUCTION exists in CDA as distinct entities and the same component can be deployed seamlessly across these environments without the need for manual handling and configuration.
  5. CDA is particularly adept at enforcing governance and compliance. It provides all the necessary tools to comply with a team’s internal processes without having to design checks and balances and fail-safe mechanisms. It will further audit deployments to ensure that everything goes smoothly and without error, all the time.

See also: