Enterprise DevOps for Architects

Jeroen Mulder

• Publisher: Packt Publishing
• Year: 2021
• ISBN:
  9781801811705
• Edition: 1
• Topic: Ciencia de la computación
• Subtopic: Aplicaciones empresariales

An architect's guide to designing, implementing, and integrating DevOps in the enterpriseKey Features• Design a DevOps architecture that is aligned with the overall enterprise architecture• Design systems that are ready for AIOps and make the move toward NoOps• Architect and implement DevSecOps pipelines, securing the DevOps enterpriseBook DescriptionDigital transformation is the new paradigm in enterprises, but the big question remains: is the enterprise ready for transformation using native technology embedded in Agile/DevOps? With this book, you'll see how to design, implement, and integrate DevOps in the enterprise architecture while keeping the Ops team on board and remaining resilient. The focus of the book is not to introduce the hundreds of different tools that are available for implementing DevOps, but instead to show you how to create a successful DevOps architecture. This book provides an architectural overview of DevOps, AIOps, and DevSecOps – the three domains that drive and accelerate digital transformation. Complete with step-by-step explanations of essential concepts, practical examples, and self-assessment questions, this DevOps book will help you to successfully integrate DevOps into enterprise architecture. You'll learn what AIOps is and what value it can bring to an enterprise. Lastly, you will learn how to integrate security principles such as zero-trust and industry security frameworks into DevOps with DevSecOps. By the end of this DevOps book, you'll be able to develop robust DevOps architectures, know which toolsets you can use for your DevOps implementation, and have a deeper understanding of next-level DevOps by implementing Site Reliability Engineering (SRE).What you will learn• Create DevOps architecture and integrate it with the enterprise architecture• Discover how DevOps can add value to the quality of IT delivery• Explore strategies to scale DevOps for an enterprise• Architect SRE for an enterprise as next-level DevOps• Understand AIOps and what value it can bring to an enterprise• Create your AIOps architecture and integrate it into DevOps• Create your DevSecOps architecture and integrate it with the existing DevOps setup• Apply zero-trust principles and industry security frameworks to DevOpsWho this book is forThis book is for enterprise architects and consultants who want to design DevOps systems for the enterprise. It provides an architectural overview of DevOps, AIOps, and DevSecOps. If you're looking to learn about the implementation of various tools within the DevOps toolchain in detail, this book is not for you.

Section 1: Architecting DevOps for Enterprises

The objective of this first part is to give guidelines and guardrails to help you develop an architecture for DevOps within enterprises. After completion, you will be able to define a DevOps architecture that is aligned with enterprise architecture. You will be able to work with (business) service-level agreements (SLAs) and key performance indicators (KPIs) in DevOps components and work according to the VOICE (Value, Objectives, Indicators, Confidence, Experience) model, controlling DevOps projects in enterprise business environments.

The following chapters will be covered under this section:

• Chapter 1, Defining the Reference Architecture for Enterprise DevOps
• Chapter 2, Managing DevOps from Architecture
• Chapter 3, Architecting for DevOps Quality
• Chapter 4, Scaling DevOps
• Chapter 5, Architecting Next-Level DevOps with SRE

Chapter 1: Defining the Reference Architecture for Enterprise DevOps

This chapter is an introduction to DevOps architecture for the enterprise. First, we'll look at the business of an enterprise. The business sets its goals and with that, defines the criteria for IT delivery, which supports these business goals. Therefore, the DevOps architecture must be aligned with the enterprise architecture. In this chapter, we will learn how to set up the reference architecture and design the different DevOps components while working with the VOICE model. Next, we'll learn how to deal with service levels and key performance indicators in DevOps models.

By the end of this chapter, you will have a clear view of how to start using the architecture and defining a DevOps strategy. An important lesson you'll learn in this chapter is that setting up DevOps in an enterprise becomes more complicated when organizations have outsourced large parts of their IT delivery. During this chapter, you will learn how to engage DevOps in enterprises with sourcing models.

We're going to cover the following main topics:

• Introducing DevOps in IT delivery
• Creating a reference architecture
• Introducing DevOps components
• Understanding SLAs and KPIs in DevOps
• Working with the VOICE model

Introducing DevOps in IT delivery

This book will focus on implementing and scaling DevOps in large enterprises. Before we get into the specific challenges of an enterprise, we need to have a common understanding of DevOps.

Somewhere, businesses and their leaders must have thought that it was a good idea to put developers and operators into one team. In essence, DevOps is the development and operations stages working as one team, on the same product and managing it. You build it, you run it.

DevOps has gained a lot of momentum over the past decade, especially in enterprises. But implementing DevOps turned out to be quite difficult. The reason for this is that enterprises are not organized in a structure that works for DevOps. From the last century onward, most enterprises outsourced a lot of their IT. Most of the IT muscles of a major enterprise are therefore still with system integrators and software houses. DevOps becomes more difficult when development is done by a software house and operations is outsourced to a system integrator.

DevOps starts with the business. By bringing teams together into a development and operations environment that traditionally work in silos, an enterprise can speed up development and release new products and services. The rationale behind this is that less time is needed to do handovers between development and operations. Also, by removing the barrier between development and operations, the quality of products will improve since DevOps includes quality assurance, testing, and security. Customer feedback is continuously evaluated and included in new iterations of the product.

The benefits of DevOps are as follows:

• It brings business, development, and operations together, without silos.
• Enterprises can respond faster to demands from the market because they're absorbing continuous feedback.
• Products are continuously improved and upgraded with new features, instead of planning for major next releases.
• Through automation in DevOps pipelines, enterprises can reduce costs in terms of both development and operations and, at the same time, improve the quality of their products.

It starts with the business and thus the starting point is the enterprise architecture. This is where the business goals are set and we define how these goals will be met. IT delivery is key to meeting these goals. In large enterprises, the architecture also defines the IT delivery processes and the demarcation between these processes. We will look at IT delivery and its processes in more detail in the next section.

Understanding IT delivery in enterprises

As we mentioned at the beginning of this section, large enterprises typically have an operating model that is based on outsourcing. This makes implementing DevOps more complicated. The enterprise architect will have to have a very clear view of the demarcation between the different processes and who's responsible for fulfilling these processes. Who is responsible for what, when, and why? The next question is, how does it map to DevOps?

First, we need to understand what the main processes are in IT delivery. These processes are as follows:

• Business demand: A business needs to understand what the requirements are for a product that it delivers. These requirements are set by the people who will use the product. Customers will demand a product that meets a specific functionality and quality. The architecture must focus on delivering an end product that satisfies the needs of the customers of an enterprise. IT delivery is a crucial part of delivering an end-product. In DevOps, an assigned product owner makes sure that the product meets the requirements. The product owner will have to work closely with the enterprise architect. In the Creating a reference architecture section, we will learn that the enterprise architecture and DevOps are complementary.
• Business planning: Once the demand is clear, the product needs to be scoped. In DevOps, product teams typically start with a Minimum Viable Product (MVP), a first iteration of the product that does meet the requirements of the customer. When designing the MVP, processes need to be able to support the development and operations of that product. Hence, business planning also involves quality management and testing, two major components of IT delivery. This needs to be reflected in the architecture.
• Development: In DevOps, the product team will work with user stories. A team must break down the product into components that can be defined as deliverables. For this, we must have a clear definition of the user story. A user story always has the same format: As a [function of the user] I want to [desire of the user] so that I [description of the benefits a user will get if the function has been delivered and ...