Skip to main content

Orchestration vs. Automation

It is important to understand the difference between orchestration and automation for any DevOps continuous delivery pipeline initiative. We orchestrate processes and we automate the activities within the process. In a recent DevOps Test Engineer (DTE) certification class I learned how to deconstruct the DevOps pipeline. Understanding the constructs of the pipeline and what your test strategies are will prove helpful for both the orchestration and automation of your delivery pipeline. Benefits of that knowledge generate better alignment and cadence with the business demand and greater deployment velocity. Orchestration and automation take advantage of standardization throughout the DevOps pipeline for integrated tools, integrated code, integrated build and integrated test all the way through. The results? Not only can we deliver product faster but that product or service is now delivered into an anti-fragile, secure and stable environment. 

Confirmation that the process is repeatable ensures that it can be orchestrated. 

You can get more details about how to define, design or improve processes in the Certified Process Design Engineer class, while the focus for this blog is on the orchestration and automation of the process for a DevOps or Continuous Delivery pipeline. You can achieve the overall orchestration by automating the activities that make up the process. Leaders should understand that the process should be comprised of many decoupled activities because this allows for reuse of automation across the entire organization. 

Be sure to recognize the difference between orchestration and automation but also how they relate to one another. Orchestration is about integrating and instrumenting process. Automation is about automating activities within a process. There is a difference, and if understood and performed correctly each should play off one another to result in being more than effective with less time, money and resources spent.

Cost savings throughout and higher customer satisfaction as you increase your capability to respond to dynamic business requirements requires a commitment to ongoing improvement.

To learn more; consider the following ITSM Academy certification courses:
DevOps Test Engineer (DTE)

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

From the Four Ps to the Four Dimensions: ITIL (Version 5)

By Donna Knapp  and Lisa Schwartz For years, people , process , and technology (PPT) provided a widely recognized framework for balancing and integrating the components needed to achieve effective performance and outcomes. In the ITIL v3 Service Design publication, this perspective expanded to the four Ps: people , processes , products , and partners . ITIL 4 developed these ideas further through the four dimensions of service management. ITIL (Version 5) carries the same four dimensions forward into digital product and service management, emphasizing their importance throughout the product and service lifecycle. The four dimensions are: Organizations and people Information and technology Partners and suppliers Value streams and processes These dimensions provide complementary perspectives for managing digital products and services. They apply across the ITIL Value System, including its management practices and the activities through which products and ser...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...