Page
1
(This page has no text content)
Page
2
SAP PRESS is a joint initiative of SAP and Rheinwerk Publishing. The know-how offered by SAP specialists combined with the expertise of Rheinwerk Publishing offers the reader expert books in the field. SAP PRESS features first-hand information and expert advice, and provides useful skills for professional decision-making. SAP PRESS offers a variety of books on technical and business-related topics for the SAP user. For further information, please visit our website: http://www.sap-press.com. Bernd Öggl, Michael Kofl er Git: Project Management for Developers and DevOps Teams 2023, 407 pages, paperback and e-book www.sap-press.com/5555 Bernd Öggl, Michael Kofler Docker: Practical Guide for Developers and DevOps Teams 2023, 491 pages, paperback and e-book www.sap-press.com/5650 Kevin Welter Kubernetes: Practical Guide for Developers and DevOps Teams 2024, 401 pages, paperback and e-book www.sap-press.com/5964 Metin Karatas Developing AI Applications: An Introduction 2024, 402 pages, paperback and e-book www.sap-press.com/5899 Michael Kofler Scripting: Automation with Bash, PowerShell, and Python 2024, 470 pages, paperback and e-book www.sap-press.com/5851
Page
3
Sujeevan Vijayakumaran DevOps Frameworks, Techniques, and Tools
Page
4
Imprint This e-book is a publication many contributed to, specifically: Editor Meagan White Acquisitions Editor Hareem Shafi German Edition Editor Christoph Meister Copyeditor Lauren Miorcec Cover Design Graham Geary Photo Credit iStockphoto: 1254474435/© bloodua; Shutterstock: 2151327127/© sak- kmesterke Layout Design Vera Brauner Production E-Book Eric Wyche Typesetting E-Book III-satz, Germany We hope that you liked this e-book. Please share your feedback with us and read the Service Pages to find out how to contact us. The Library of Congress has cataloged the printed edition as follows: 2024044381 ISBN 978-1-4932-2670-2 (print) ISBN 978-1-4932-2671-9 (e-book) ISBN 978-1-4932-2672-6 (print and e-book) 1st edition 2025 1st German edition published 2025 by Rheinwerk Verlag © 2025 by: Rheinwerk Publishing, Inc. 2 Heritage Drive, Suite 305 Quincy, MA 02171 USA info@rheinwerk-publishing.com Represented in the E.U. by: Rheinwerk Verlag GmbH Rheinwerkallee 4 53227 Bonn Germany service@rheinwerk-verlag.de
Page
5
(This page has no text content)
Page
6
Contents 1 Introduction 15 1.1 Culture ........................................................................................................................................ 16 1.2 Technology ............................................................................................................................... 17 1.3 My Path to DevOps and to This Book ........................................................................... 17 1.4 Target Audience ..................................................................................................................... 19 1.5 The Structure of the Book .................................................................................................. 20 1.6 Feedback .................................................................................................................................... 20 1.7 Thank You! ................................................................................................................................ 21 2 What Is DevOps? 23 2.1 DevOps: The Big Picture ..................................................................................................... 23 2.1.1 CALMS ........................................................................................................................ 25 2.1.2 The Three Ways ....................................................................................................... 28 2.1.3 Conclusion on the Three Ways and the CALMS Model .............................. 35 2.2 Misunderstandings about DevOps ................................................................................ 36 2.2.1 Too Strong a Focus on Automation .................................................................. 36 2.2.2 With DevOps, but without Tests! ..................................................................... 37 2.2.3 Incorrect Understanding of Team Structuring ............................................. 38 2.2.4 Not Tearing Down All the Walls ........................................................................ 39 2.2.5 Tools over Processes over People ...................................................................... 40 2.2.6 One to One Copies of Working Methods from Other Companies ......... 41 2.3 The DevOps Software Development Lifecycle ......................................................... 42 2.4 Summary ................................................................................................................................... 45 3 The Example Company 47 3.1 nicely-dressed.com ............................................................................................................... 48 3.2 The Development Model .................................................................................................... 48 3.3 The Business Team: Requirements Analysis ............................................................. 497
Page
7
Contents3.4 The Architecture Team: Design of the Application ................................................ 50 3.5 The Development Teams ................................................................................................... 50 3.5.1 The Development Process ................................................................................... 51 3.5.2 Integrations with Obstacles ............................................................................... 51 3.6 The Quality Assurance Team ............................................................................................ 52 3.7 The Operations Team: The Ops in DevOps ................................................................. 53 3.7.1 Manual Build of the Project ................................................................................ 55 3.7.2 Deployment with Obstacles ............................................................................... 55 3.7.3 Alarm from the Monitoring System ................................................................. 56 3.8 The Infrastructure Team ..................................................................................................... 56 3.9 The Security Team ................................................................................................................. 57 3.10 Summary ................................................................................................................................... 58 4 Project Management and Planning 61 4.1 The First Step: The Agile Mindset ................................................................................... 61 4.2 Project Management for Everyone? ............................................................................. 64 4.2.1 Jira Can Do (Almost) Everything ........................................................................ 65 4.2.2 People over Processes ........................................................................................... 66 4.2.3 Good Project Management outside of Jira .................................................... 67 4.2.4 More than Just a Project Management Tool ................................................. 69 4.2.5 Project Management at nicely-dressed.com ................................................. 71 4.3 Summary ................................................................................................................................... 72 5 Collaboration when Coding 73 5.1 Typical Problems with Managing the Source Code ................................................ 73 5.1.1 Organization of the Code .................................................................................... 74 5.1.2 Isolation for Supposed Security Reasons ........................................................ 75 5.1.3 Long Development Times Hindering Quick Security Fixes ....................... 76 5.1.4 Development Workflow without a Proper Structure ................................. 77 5.1.5 Big Bang Integrations ............................................................................................ 77 5.1.6 Code Reviews Could Help .................................................................................... 78 5.1.7 Technical Debt ......................................................................................................... 79 5.1.8 High Learning Curve due to Lack of Documentation ................................. 80 5.2 Improve the Organization of the Code ........................................................................ 818
Page
8
Contents5.3 There Is No Way around Git .............................................................................................. 83 5.3.1 Git Solutions at a Glance ..................................................................................... 83 5.3.2 Development Workflows with Git .................................................................... 84 5.3.3 Source Code Management at nicely-dressed.com ...................................... 90 5.4 Code Reviews and Pair Programming .......................................................................... 91 5.4.1 Code Reviews ........................................................................................................... 91 5.4.2 Simplify Code Reviews .......................................................................................... 97 5.4.3 Pair Programming .................................................................................................. 99 5.5 Inner Sourcing: Sharing Code within the Company ............................................... 102 5.5.1 Open Source ............................................................................................................. 103 5.5.2 The Path to Inner Sourcing .................................................................................. 104 5.5.3 Advantages of Inner Sourcing ............................................................................ 106 5.5.4 Monorepositories ................................................................................................... 108 5.6 Summary ................................................................................................................................... 111 6 Continuous Integration and the Build Process 113 6.1 Typical Problems in the Build Process .......................................................................... 113 6.1.1 Onboarding with Stumbling Blocks ................................................................. 114 6.1.2 Build Difficulties Due to Infrequent Integrations ........................................ 116 6.1.3 Only a Few Tests ..................................................................................................... 117 6.1.4 A Build Server behind Closed Doors ................................................................. 118 6.2 Modern Build Management ............................................................................................. 119 6.3 Continuous Integration ...................................................................................................... 122 6.4 The Continuous Integration Server and the Pipelines .......................................... 126 6.4.1 The Basic Structure of a Pipeline ....................................................................... 126 6.4.2 Scaling and Reproducibility ................................................................................. 128 6.4.3 Declarative Pipelines versus Scripted Pipelines ........................................... 130 6.5 Efficient Pipeline Authoring ............................................................................................. 132 6.5.1 Avoid Central Pipelines ......................................................................................... 132 6.5.2 Provide Pipeline Building Blocks ........................................................................ 133 6.5.3 Create Visibility ....................................................................................................... 134 6.6 Overview of Continuous Integration Servers ........................................................... 134 6.6.1 Jenkins ........................................................................................................................ 136 6.6.2 GitLab CI/CD ............................................................................................................. 142 6.6.3 GitHub Actions ........................................................................................................ 146 6.6.4 Other Continuous Integration Servers and Tools ........................................ 150 6.6.5 Continuous Integration at nicely-dressed.com ............................................ 151 6.7 Summary ................................................................................................................................... 1529
Page
9
Contents7 Quality Assurance 153 7.1 Typical Problems with Testing ......................................................................................... 153 7.1.1 Teams in Their Silos ............................................................................................... 154 7.1.2 Different Understandings of Requirements ................................................. 155 7.1.3 The Number of Bugs as a Metric ....................................................................... 156 7.1.4 Is It Fixed Yet? .......................................................................................................... 157 7.2 Testing as Part of the DevOps Process ......................................................................... 158 7.2.1 Tests in the Build Pipeline ................................................................................... 160 7.2.2 Different Tests for Different Tasks ................................................................... 162 7.2.3 Automate Tests ....................................................................................................... 164 7.2.4 Test-Driven Development ................................................................................... 169 7.3 Summary ................................................................................................................................... 171 8 Continuous Delivery and Deployment 173 8.1 Typical Release Management Problems ..................................................................... 173 8.1.1 Separate Handling of Changes and Documentation ................................. 174 8.1.2 Lengthy Release Process ....................................................................................... 175 8.1.3 Automations That Are Not Worthwhile ......................................................... 176 8.1.4 Hostilities between the Teams .......................................................................... 176 8.1.5 Deployment on Production Systems with Obstacles ................................. 177 8.1.6 Conclusion ................................................................................................................ 178 8.2 Implementing Continuous Delivery and Deployment .......................................... 179 8.2.1 Bringing Development and Operations Together ....................................... 179 8.2.2 QA, Staging, and Production Environments .................................................. 185 8.2.3 Deployment on Fridays ......................................................................................... 190 8.3 Build Management for Deployments ........................................................................... 191 8.3.1 The Question of Version Numbers ................................................................... 192 8.3.2 Packaging .................................................................................................................. 193 8.3.3 Containerization ..................................................................................................... 194 8.3.4 Container Registry and Package Registry ....................................................... 196 8.4 Rollbacks, Canaries, and Feature Flags ........................................................................ 198 8.4.1 Rollbacks .................................................................................................................... 199 8.4.2 Step-by-Step Activation Using Blue-Green and Canary Deployments ............................................................................................................ 200 8.4.3 Feature Flags ............................................................................................................ 20310
Page
10
Contents8.5 Deployment Targets ............................................................................................................. 205 8.5.1 Orchestrating Deployments with Kubernetes ............................................. 205 8.5.2 Orchestrating Deployments at nicely-dressed.com ................................... 219 8.6 Summary ................................................................................................................................... 219 9 Operating the Service 221 9.1 Typical Problems with Operating Services ................................................................. 221 9.1.1 Lengthy Infrastructure Planning ....................................................................... 222 9.1.2 Hardware Exchange with Obstacles ................................................................ 222 9.1.3 Unfavorable Server Utilization .......................................................................... 223 9.1.4 Common Outages during the Night ................................................................ 224 9.2 Breaking Up the Highly Coupled Infrastructure Architecture ........................... 226 9.2.1 Cattle, not Pets ........................................................................................................ 226 9.2.2 Abstracting the Infrastructure ........................................................................... 228 9.2.3 Containers for Faster Deployments ................................................................. 231 9.3 Cloud Computing ................................................................................................................... 233 9.3.1 What Is the Cloud? ................................................................................................. 233 9.3.2 Cloud Models ........................................................................................................... 234 9.3.3 Service Models ......................................................................................................... 235 9.3.4 Cloud Native ............................................................................................................. 240 9.3.5 The Cloud at nicely-dressed.com ...................................................................... 242 9.4 Stronger Collaboration between Development and Operations ..................... 243 9.4.1 Everyone Should Be Ready ................................................................................... 243 9.4.2 Blameless Post-Mortems ..................................................................................... 245 9.4.3 Communication Solutions and ChatOps ........................................................ 247 9.5 Configuration Management: Everything as Code .................................................. 249 9.5.1 Infrastructure as Code with Terraform ........................................................... 250 9.5.2 Ansible versus Puppet ........................................................................................... 253 9.6 Chaos Engineering ................................................................................................................ 258 9.6.1 Making Systems Fail .............................................................................................. 258 9.6.2 Chaos Engineering without Chaos, but with a Plan ................................... 260 9.7 Reliability Engineering ........................................................................................................ 262 9.7.1 Site Reliability Engineering ................................................................................. 263 9.7.2 Database Reliability Engineering ...................................................................... 264 9.8 Summary ................................................................................................................................... 26511
Page
11
Contents10 From Monitoring to Observability 267 10.1 No Visibility at nicely-dressed.com ............................................................................... 268 10.1.1 Service Outages Happen Every Day .................................................................. 268 10.1.2 Performance, Performance! ................................................................................ 272 10.1.3 Logs ............................................................................................................................. 274 10.2 With Insight Comes Foresight ......................................................................................... 275 10.2.1 Observability Engineering ................................................................................... 276 10.2.2 Insights into Processes with Tracing ................................................................ 278 10.2.3 A/B Tests .................................................................................................................... 279 10.2.4 Business Monitoring ............................................................................................. 281 10.3 Tools for Monitoring, Observability, and Tracing ................................................... 282 10.3.1 Monitor Systems with Icinga and Nagios ...................................................... 283 10.3.2 Monitoring with Metrics and Time Series Databases ................................ 284 10.3.3 Data Visualization with Grafana ....................................................................... 292 10.3.4 Error Tracking ........................................................................................................... 294 10.3.5 Distributed Tracing ................................................................................................ 295 10.3.6 Logging ....................................................................................................................... 296 10.3.7 Service Meshes ........................................................................................................ 297 10.3.8 Observability Platforms ........................................................................................ 298 10.3.9 Monitoring and Observability at nicely-dressed.com ................................ 300 10.4 Availability ............................................................................................................................... 300 10.4.1 Service Level Agreements .................................................................................... 301 10.4.2 Service Level Objectives ........................................................................................ 302 10.4.3 Service Level Indicators ......................................................................................... 303 10.4.4 Error Budgets ........................................................................................................... 303 10.5 Summary ................................................................................................................................... 304 11 Security and Compliance 307 11.1 Security Disrupts the Agile Waterfall ........................................................................... 308 11.2 DevOps with a Separate Security Team ...................................................................... 310 11.2.1 To Deploy or Not to Deploy? ............................................................................... 311 11.2.2 The Search for Undocumented Dependencies ............................................. 312 11.2.3 Frustration and Blocking ...................................................................................... 313 11.3 DevSecOps: Building Security into DevOps ............................................................... 314 11.3.1 The DevSecOps Team Structure ........................................................................ 315 11.3.2 Shift Left: Find Errors Earlier ............................................................................... 316 11.3.3 Inner Sourcing Ensures Formal Security ......................................................... 31712
Page
12
Contents11.3.4 Security as an Integral Part of the Development Process ......................... 318 11.3.5 Dealing with Mistakes .......................................................................................... 319 11.4 Tools for Higher Security .................................................................................................... 321 11.4.1 Dashboards and Reporting ................................................................................. 321 11.4.2 Pull and Merge Requests ..................................................................................... 322 11.4.3 Security Scanners in Detail .................................................................................. 322 11.5 Supply Chain Security .......................................................................................................... 329 11.5.1 Attacks on the Supply Chain ............................................................................... 330 11.5.2 Software Bill of Materials .................................................................................... 332 11.5.3 Security of the Build and Deployment Server ............................................... 332 11.5.4 Secure User Accounts ............................................................................................ 333 11.5.5 No Code Is Good Code ........................................................................................... 334 11.5.6 Security at nicely-dressed.com .......................................................................... 335 11.6 Compliance ............................................................................................................................... 335 11.6.1 Define Compliance Guidelines .......................................................................... 336 11.6.2 Manual Compliance .............................................................................................. 338 11.6.3 Fully Automated Compliance ............................................................................. 339 11.6.4 Compliance at nicely-dressed.com ................................................................... 345 11.7 Summary ................................................................................................................................... 345 12 Successfully Implementing the DevOps Transformation 347 12.1 Introducing a DevOps Culture ......................................................................................... 347 12.1.1 Bottom-Up or Top-Down? ................................................................................... 348 12.1.2 First Steps in the DevOps Transformation ..................................................... 350 12.2 Making DevOps Success Measurable with DORA Metrics .................................. 362 12.2.1 DORA Metric 1: Deployment Frequency ......................................................... 363 12.2.2 DORA Metric 2: Lead Time ................................................................................... 364 12.2.3 DORA Metric 3: Change Failure Rate ............................................................... 365 12.2.4 DORA Metric 4: Time to Restore Service ......................................................... 366 12.2.5 DORA Metric 5: Operational Performance and Reliability ........................ 366 12.2.6 Findings from the State of DevOps Report .................................................... 367 12.3 Value Stream Mapping ....................................................................................................... 368 12.3.1 The Value Stream of a Pizzeria ........................................................................... 369 12.3.2 The Value Stream at nicely-dressed.com ....................................................... 370 12.3.3 Implementation of Value Stream Mapping .................................................. 371 12.4 Summary ................................................................................................................................... 37513
Page
13
Contents14 13 DevOps Platforms 377 13.1 Toolchain Complexity .......................................................................................................... 378 13.1.1 Step 0: Toolchains Grow Historically ............................................................... 378 13.1.2 Step 1: Multiple Toolchains to Increase Maintainability .......................... 379 13.1.3 Step 2: Standardized Tools, but Still with a Lot of Duct Tape ................. 381 13.1.4 Step 3: DevOps Platforms .................................................................................... 382 13.2 DevOps Platforms at a Glance ......................................................................................... 384 13.2.1 GitLab ......................................................................................................................... 384 13.2.2 GitHub ........................................................................................................................ 385 13.2.3 Azure DevOps .......................................................................................................... 385 13.2.4 Atlassian .................................................................................................................... 386 13.2.5 Other Platforms ...................................................................................................... 386 13.3 Summary ................................................................................................................................... 387 14 Beyond Culture and Tools 389 14.1 The Role of AI in DevOps .................................................................................................... 389 14.1.1 Making Work Easier with AI-Supported Code Generation? ..................... 390 14.1.2 More Code Leads to Higher Review Requirements! ................................... 392 14.1.3 AI-Supporting Features ........................................................................................ 393 14.1.4 Data Protection and Privacy ................................................................................ 394 14.1.5 It’s the Overall Concept That Counts! ............................................................. 395 14.2 DataOps, MLOps, and AIOps ............................................................................................. 397 14.2.1 DataOps ..................................................................................................................... 397 14.2.2 MLOps ........................................................................................................................ 398 14.2.3 AIOps .......................................................................................................................... 398 14.3 DevOps as a Job ...................................................................................................................... 399 14.3.1 The Question of DevOps Engineers .................................................................. 399 14.3.2 Soft Skills ................................................................................................................... 401 14.3.3 The Technical DevOps Learning Path .............................................................. 402 14.4 Summary ................................................................................................................................... 410 The Author ............................................................................................................................................... 411 Index .......................................................................................................................................................... 413 Service Pages ..................................................................................................................................... Legal Notes ......................................................................................................................................... I
Page
14
Chapter 1 Introduction “Nothing is as constant as change.” This quote is now almost 2,000 years old but is more relevant than ever: Product devel- opment cycles need to be faster today to meet constantly changing requirements, over which we often have no direct influence. A recent event that illustrates this reality is the COVID-19 pandemic, which highlighted how crucial flexibility is. The pandemic not only required that many people quickly switch from office jobs to remote work, but it also affected how work was organized in the first place. Suddenly, familiar methods and processes of in-office work had to be adapted to remote working environments from one day to the next. This challenge affected not only pure IT com- panies but also other organizations, authorities, schools, and associations. Companies that were able to quickly adapt both their internal workflows and business models to changing conditions gained a significant competitive advantage. The pan- demic clearly shows how rapidly requirements can change and how important it is to adapt with agility. In this constantly changing environment, DevOps culture plays a crucial role. DevOps promotes collaboration between the development (Dev) and operations (Ops) teams to accelerate processes, improve quality, and increase flexibility at the same time. This concept enables companies to adapt effectively to changing requirements and thus operate successfully in a dynamic world. For example, one notable legal change that probably affected all companies in Ger- many was the decision on June 3, 2020, to reduce the VAT rate from 19% to 16% for six months as of July 1, 2020. Between this decision and the changeover, there was only just under four weeks to implement, test, and roll out the necessary changes. Recent events that disrupt business requirements have shown how adaptable compa- nies and organizations can be when the need arises. However, instead of making quick adjustments only in exceptional situations, companies could make their processes more efficient if they made such adjustments more regularly as part of their normal operations. This would benefit not only the companies themselves but also all the users of their services. And the benefits of regularly adjusting processes doesn’t apply only to hip IT start- ups working on apps and websites. In fact, many companies—and even public authorities—are already IT organizations at their core, even if they do not necessarily15Personal Copy for Jaleel Hussain, alex76alex43@gmail.com
Page
15
1 Introductionoffer pure software products. For example, a bank’s core business is largely based on the software needed to manage bank accounts and services. So, in a sense, a bank is more of a software development company with an additional banking license. It is therefore not surprising that some banks, such as ING, describe themselves in exactly this way. If you already know a little about IT, the idea of continuously improving processes will sound familiar to you: After all, that’s the basic idea behind agile software develop- ment. But isn’t this book supposed to be about DevOps, not agile software develop- ment? This is precisely where the first good question arises: What is agility, what is DevOps, how are the two connected, and how do they diverge? But let’s take a step back because perhaps the most important question is actually: Why do it at all? Far too often, people follow trends of all kinds and take actions based on what everyone else is doing. However, it makes much more sense to ask why a certain approach is trending and then introduce changes based on this analysis. This book answers these questions and many others. It is divided into two overarching sections: culture and technology. We start by looking at culture: we cover the concepts, advantages, and disadvantages of DevOps without going into too much detail about individual technical tools. However, we cannot entirely ignore the IT tool landscape. As this landscape is constantly changing, I do not cover too many specific details about each tool; instead, you will find an overview of the state of the art, with a focus on the basic DevOps technology to consider and the concepts that underlie it. We don’t want this book to be dry and theoretical; therefore, we look at the whole topic through the lens of a fictional company, which is presented in Chapter 3. This company has not yet relied on DevOps principles. Chapter by chapter, the company introduces more and more DevOps principles to show what a DevOps transformation can look like. After all, very few companies will be able to start a DevOps transformation on a greenfield. 1.1 Culture One thing is very important: Understanding DevOps culture is more important than understanding the actual tools. Because DevOps is a culture, it is a way of working together as a team. Many people have a misunderstanding of DevOps, which is why it is important that you understand DevOps culture properly before we look at technical tools in this book. The term “DevOps” is a portmanteau of “development” and “operations.” It is about breaking down the walls between the development team and the operations team, allowing them to work together toward a common goal: the continuous development and provision of the software-based solution.16 © 2025 by Rheinwerk Publishing Inc., Boston (MA)
Page
16
1.3 My Path to DevOps and to This BookIn this book, I describe what DevOps culture is, what it is not, and where it overlaps with other ways of working. Most importantly, DevOps must be lived throughout the orga- nization, from the top to the bottom of the hierarchy. Likely the most difficult challenge for you, and especially for your organization, is to flip the switch in your head; implementing DevOps culture requires a change of per- spective. It also requires everyone in the organization to adapt to different tasks and perspectives: Developers will sometimes have to be on call, admins should know what a pull request is, and everyone will ultimately be responsible for the security and reli- ability of the application. 1.2 Technology Even though DevOps is essentially a culture, and its description alone could fill the pages of this book, I also cover some tools of the DevOps landscape so that you can bet- ter understand the current state of the art. However, I do not discuss every single tool down to the last detail; rather, I discuss the concepts of the tools so that you can understand why they in particular are used in the current DevOps tool landscape. After reading this section, you should also understand why some tools are used less frequently or where and in what combination they can be useful, especially if DevOps is implemented properly. It is important to understand that the technology is merely a tool for implementing the culture. Good tools support the culture, but even the best tools will not help you if the processes and culture are not lived in the organization. 1.3 My Path to DevOps and to This Book Many friends, acquaintances, and colleagues have asked me why I was writing a Dev- Ops book, as the tenor is that the topic is already old hat and “almost done.” Meanwhile, both smaller and larger companies claim that they are already doing DevOps. The real- ity, however, is a little different. My motivation for this project has its roots at the beginning of my IT career. In 2011, I started studying while also working at a medium-sized company and wanted to even- tually become a software developer. However, I never really got around to program- ming back then, as there was much more to do to improve the company’s development productivity. There was almost no automation at all in this company; numerous tasks were done manually. This meant that the various teams lost a lot of time, did not work well together, and did not use the tools for building and testing efficiently. And here I'm writing only about the development workflow: What happened to the software when it17Personal Copy for Jaleel Hussain, alex76alex43@gmail.com
Page
17
1 Introductionwas rolled out barely reached the development team because the finished package was essentially thrown “over the wall” to another team from a service provider, which then took over operations. What happened after that? I have no idea because there was never any feedback. In addition, the development team had no environments in which to test the software close to production. Whether a change to the software worked was always a big ques- tion that nobody could really answer. As a stopgap solution, employees set up many small test environments by hand, which had to be cleaned up and reinstalled manually time and time again, wasting a lot of time. The test systems were never really clean. Many of these shortcomings are probably still typical of small- or medium-sized com- panies today, especially older companies. The statement “But we’ve always done it this way!” is heard often enough, and many companies lack the will to constantly improve their processes and learn new approaches, so there are practically no further training measures in such companies. Unfortunately, after a few decades of standstill, the devel- opers’ work has been made unnecessarily difficult, severely impacting productivity. Over time, I introduced automation at this company, simplified the test setup for the development team, created automated test environments, and made everyday devel- opment more efficient and enjoyable. However, I quickly realized that automation is one thing, but its use and acceptance from managers and directors is quite another. Even if most of the automation could have been used with little effort, it was essential that people got to grips with it. This only works if there is time for it and process improvements are also desired. Even though I was not familiar with DevOps as a term and culture at the time—both were still in their infancy—it quickly became clear to me that this culture must be firmly anchored in the company. There must be the will to constantly improve, to question complex processes, and to cut out any that are deemed useless. The entire organization must actively break down barriers between teams and areas of responsi- bility so that work can be carried out efficiently. While I worked at this company, I attended two different universities in succession: first a university of applied sciences and then a university where I completed my mas- ter’s degree. I completed one or two group projects in which I had to work with a team of students to develop and deploy a software project. I noticed that although my vari- ous team members had decent programming skills, hardly anyone had ever worked on a “real” software project. This meant that although basic development knowledge was available in theory, hardly anyone I worked with on these projects had any idea or practical experience of what modern software development should look like today, from basic tools such as Git and continuous integration tooling to correct reviewing, testing, and deployment proce- dures.18 © 2025 by Rheinwerk Publishing Inc., Boston (MA)
Page
18
1.4 Target AudienceAlthough many of these topics were mentioned at certain points in my courses, the students lacked practical experience to bring the individual points together. A university project like this would actually be a good starting point for trying out Dev- Ops techniques, as it would give you an empty playground where you can try out new processes and tools. Companies tend to be confronted with projects that are older than most students themselves, making it much more difficult to make the leap to new Dev- Ops techniques, as it is difficult to leave the beaten track. If you are currently in training or at university, I hope this book will help you understand the basics of modern soft- ware development according to DevOps principles at an early stage. After my studies, I had the opportunity to work in other companies as a consultant, where I often recognized a similar pattern: entrenched, rigid structures and processes in which different teams throw tasks and problems back and forth between each other instead of working together collaboratively. This always had to do with a corporate culture that did not enable good cooperation; in some cases, the corporate culture even actively prevented it. Such a culture almost always harmed the end users: Useful functions and urgent bug fixes were often delayed in reaching them. Users were understandably dissatisfied with the products. In private conversations with friends and acquaintances in the IT scene, I often heard sim- ilar stories. I have been working as a solutions architect at GitLab since the spring of 2020 until October 2024. I mainly advised companies from Germany, Austria, and Switzerland to help them implement DevOps with GitLab. This job has made me realize that although DevOps is being used almost everywhere, including at large companies with thousands of employees, the focus is still almost exclusively on the tool landscape and, therefore, on the technology. The culture is adapted only with difficulty, if at all. All these experiences have made it clear to me that there is still a long way to go in the practical implementation of DevOps. In numerous discussions with customers, people often paint the wrong picture of DevOps or oversimplify it. With this book, I want to simplify the entry and transition into the DevOps world and thus contribute to improvements in work culture, employee satisfaction, and general productivity. 1.4 Target Audience The book is basically aimed at anyone who has a role in the software development life- cycle, including not only development teams and operations teams, but also the busi- ness teams and managers who set the direction. DevOps is relevant for everyone in an organization, and all teams must align themselves with DevOps principles; only then can the implementation be successful.19Personal Copy for Jaleel Hussain, alex76alex43@gmail.com
Page
19
1 IntroductionThe book is therefore aimed at two overlapping groups. First, it aims to provide a gen- eral, clear description of what DevOps is and how a DevOps transformation can suc- ceed. This part of the book is aimed at anyone who wants to take a closer look at DevOps. These include not only people on cross-functional teams with a focus on development and operations, but also those in management with decision-making powers. After all, DevOps cannot be realistically implemented without support from the top. And this requires a profound understanding of the processes and dynamics in the entire software development lifecycle, from planning to programming and deliv- ery. Second, the section discussing tools and technology is mainly aimed at those who work on a DevOps team on a daily basis. However, decision-makers can also gain some insight from this section; with a better understanding of the technology, they will be able to better understand the value of the tools. Time and again, I have seen companies and their employees calling for a tool like Kubernetes without having considered whether it would be the right tool for their teams. So before you make a gut decision on which tools and techniques to use, you should ensure that you understand their under- lying concepts. 1.5 The Structure of the Book The next chapter begins with a definition of DevOps. To contextualize this definition, Chapter 3 introduces Nicely Dressed Ltd., an example company used to show you the pitfalls of the old world—of traditional waterfall development procedures—and how you can do things better in the new DevOps world. The individual stages of the DevOps lifecycle are covered in Chapter 3 through Chapter 11, using Nicely Dressed Ltd. repeatedly as an example throughout. Each chapter con- tains both a cultural and technical part and includes illustrative examples to describe the DevOps principles so that you also get to know the tools and techniques that are relevant in each stage. The end of each section includes a summary for reflection to remind you of the most important aspects of the chapter, share a few insights from practice with you, and ide- ally provide you with ideas that you can use to reflect on your own organization and technology. Hopefully, you will find a few starting points that you can adapt to your organization. 1.6 Feedback This book is not just about technology. On the contrary, it’s about work culture. And that is my biggest challenge. While there is usually a clear solution to technical prob- lems, this is not the case with problems related to culture.20 © 2025 by Rheinwerk Publishing Inc., Boston (MA)
Page
20
1.7 Thank You!When it comes to changing your work culture, there are a lot of truths, and you can get a lot of things right and a lot more wrong. There are many pitfalls and numerous mis- takes that can cause frustration. And unfortunately, there is almost never a universal solution that fits all companies, all teams, and all people. Ultimately, many factors in this book depend on various other factors: the industry, the size of the company, and the existing corporate culture. And that’s exactly why I’m interested in your feedback. If you have any points that you think are missing here or should be dealt with in more depth, send me an email at mail@svij.org. I am very interested in what has and has not worked well for you and what you have learned from the process. 1.7 Thank You! A book like this cannot be realized without active support at various levels—both pro- fessional and nonprofessional. Accordingly, I must thank a number of people, and I hope that I have not forgotten anyone. First and foremost, I would like to thank Dirk Deimeke, my mentor and advisor, who always gave me excellent feedback to help me make the book the way it is. And his help went hand in hand with the support of my editor Christoph Meister, who provided a lot of input to make the book better and better. I would also like to thank my family, most importantly my extended family, my par- ents, Rajeevan, Shrani, Maaduri, Max, and Mythili, as well as my nieces and nephews Mithra, Mira, Riaan, and Levi, who unfortunately heard far too little from me while I was busy writing. I would also like to thank my former colleagues at GitLab, who not only have contrib- uted significantly to my DevOps career but have also given me a great deal of feedback on individual minor and major points of this book: Ralf Gronkowski, Vlad Budica, Kris- tof Goossens, Alexander Dess, Timo Schuit, Manuel Kraft, Martin Brümmer, Jörn Schneeweisz, Jörg Heilig, Sarina Kraft, Andrea Obermeier, Michael Friedrich, Sander Brienen, Ted Gieschen, Julia Gätjens, Christoph Parschau, Christoph Caspar, Simon Mansfield, Idir Ouhab, Christopher Allenfort, Dominique Top, Stefania Chaplin, James Moverley, Stephen Walters, and Janina Roppelt. I have learned a lot over the past 15 years in the German Linux and open-source com- munity, mainly from my colleagues at ubuntuusers.de: Torsten Franz, Stefan Betz, Christian Klotz, Jörg Kastning, Sarah Blume, Philipp Schmidt, Christoph Volkert, and Dominik Wagenführ. Last but not least, I would also like to thank two former colleagues from my first job at otris software AG, Dr. Veit Jahns and Thomas Schmidt. And of course, a big thank-you to the listeners of my German podcast, TILpod, who have been able to listen to and empathize with the book every month.21Personal Copy for Jaleel Hussain, alex76alex43@gmail.com