E-Book, Englisch, 358 Seiten
Reihe: Packt Publishing
Cade The DevOps Solutions Handbook
1. Auflage 2026
ISBN: 978-1-83588-073-9
Verlag: Packt Publishing
Format: EPUB
Kopierschutz: 0 - No protection
Launch your DevOps career with 90 days of hands-on projects in automation, cloud, and CI/CD
E-Book, Englisch, 358 Seiten
Reihe: Packt Publishing
ISBN: 978-1-83588-073-9
Verlag: Packt Publishing
Format: EPUB
Kopierschutz: 0 - No protection
The DevOps Solutions Handbook is a hands-on, project-driven guide designed to help system administrators and aspiring engineers transition into modern DevOps roles. Instead of focusing only on theory, this book takes you through 90 days of practical projects that mirror real-world DevOps workflows used by high-performing engineering teams.
You'll begin by building strong foundations in Linux, Git, and DevOps principles, then move into Infrastructure as Code with Terraform and configuration management with Ansible. As your journey progresses, you'll containerize applications using Docker, deploy them to Kubernetes, and integrate cloud-native services and databases. The book emphasizes learning by doing. Each chapter builds on the previous one, guiding you through setting up CI/CD pipelines with Jenkins, GitHub Actions, and GitOps workflows using ArgoCD. You'll automate builds, testing, deployments, and infrastructure provisioning, creating working artifacts that reflect what DevOps engineers build every day.
By the final chapters, you'll design and deploy a full-stack, production-style application using modern DevOps tooling, bringing together infrastructure automation, containers, orchestration, and continuous delivery.
Autoren/Hrsg.
Weitere Infos & Material
1
Kickstart Your DevOps Journey
Welcome to 90 Days of DevOps! Before we dive into the world of DevOps, let me introduce myself and share the story behind this book. I'm Michael Cade, Field CTO at Veeam Software, and I have worked in the technology industry for more than 20 years. During that time, I have held a variety of roles, from building computers and servers to working in software engineering and pre-sales.
The technical community has played an important part in my journey. Over the years, I have participated in community programs run by major technology vendors, as well as informal forums where friends and peers help one another learn and grow. These experiences have made me a strong advocate for learning in public and creating content. If something I create helps even one person, I believe it is worth doing.
During my time at Veeam, I started a project called #90DaysOfDevOps as a way to learn in public and gain hands-on experience with a range of DevOps tools and practices. Having seen the need for stronger collaboration between development and operations teams throughout my career, I also wanted the project to help bridge the gap between these two areas. That project has since evolved into this book, which aims to provide you with a solid foundation in some of the key areas of DevOps.
Reading this book will not turn you into a DevOps expert overnight. Instead, I hope it will spark your curiosity and encourage you to explore the topics further. Each chapter is designed to stand on its own and uses accessible software wherever possible. The chapters explain the broader purpose behind the tools and practices being discussed and include hands-on exercises to reinforce what you learn. Above all, my goal is to make this an enjoyable and educational journey that inspires you to dive deeper into the world of DevOps.
In this first chapter, we will cover the following topics:
- What is DevOps?
- DevOps lifecycle
- DevOps and Agile
- The continuous cycle
Let's get started with an introduction to DevOps!
Download the PDF version of this book
Your purchase includes a DRM-free PDF copy of this book, the code bundle, and a range of exclusive benefits. To unlock everything, follow the section in the .
What is DevOps?
In this brief introduction, we'll cover some of the fundamentals of DevOps, including the what, why, and how of this exciting field. In the following chapters, we'll explore the tools and practices that make up the world of DevOps, including Linux, Git, cloud computing, and Infrastructure as Code, which are all critical components of a modern DevOps environment.
DevOps isn't a tool, software, or language – it's a way of doing things in software development that makes sense. It's not just for developers; everyone from operations to QA engineers can benefit from these best practices.
At its core, DevOps is about bridging the gap between development and operations. As someone who started in VMs and moved toward Ops, I've seen how this mindset can bring people together. By adopting DevOps practices, teams can reduce the time it takes to get a product or feature from ideation to production.
One key area we'll explore is the connection between DevOps and Agile methodology. When used together, these approaches enable the continuous delivery of applications.
The goal of DevOps is to shrink the software release process from potentially years to smaller, more frequent drops. It's not just about speed; it's also about breaking down silos between teams—developers, operations, and QA engineers alike.
From a DevOps perspective, development, testing, and deployment are all under one umbrella. And to make this work efficiently, we need to leverage automation.
There are two main parts when creating an application:
- , where software developers program the application and test it
- , where the application is deployed and maintained on a server or platform
DevOps is the link between the two
To get to grips with DevOps or the tasks that a DevOps engineer would be carrying out, we need to understand the tools or processes, an overview of those, and how they come together. Everything starts with the application! You will see throughout that it is all about the application when it comes to DevOps.
Developers will create an application; this can be done with many different technology stacks, and let's leave that to the imagination for now as we get into this later. This can also involve many different programming languages, build tools, and code repositories, etc. As a DevOps engineer, you won't be programming the application, but having a good understanding of the concepts of how a developer works and the systems, tools, and processes they are using is key to success. At a very high level, you are going to need to know how the application is configured to talk to all its required services or data services, and then also sprinkle a requirement of how this can or should be tested.
The application will need to be deployed somewhere; let's keep it generally simple here and make this a server. It doesn't matter where, but a server. This is then expected to be accessed by the customer or end user, depending on the application that has been created. This server needs to run somewhere: on-premises, in a public cloud, or in a container. Someone needs to create and configure these servers and get them ready for the application to run. Now, this element might land at your feet as a DevOps engineer to deploy and configure these servers.
These servers run an operating system, and generally speaking, this is going to be Linux, but we have a whole chapter where we cover some of the foundational knowledge you should gain here. It is also likely that we need to communicate with other services in our network or environment, so we also need to have that level of knowledge around networking and configuration; this might to some degree also land at the door of a DevOps engineer. We will now delve into the DevOps lifecycle.
DevOps lifecycle
As we progress through this book, you will notice a reference to these terms: Continuous Development, Testing, Deployment, and Monitor, repeatedly. As a DevOps Engineer, you'll get used to repeatability, but constantly enhancing with each repetition is what keeps things interesting. Let's take a look at a high-level view of an application from start to finish and back around again like a constant loop.
Development
Let's take a brand-new example of an application. To start with, we have nothing created—maybe as a developer, you need to discuss the requirements with your client or end user and come up with some sort of plan or requirements for your application. We then need to create our brand-new application from the requirements.
Tooling
At this stage, there is no real requirement other than choosing the IDE and programming language you wish to use to write your application.
As a DevOps engineer, this is where you'll work closely with developers to understand their needs and develop an application that meets those needs.
Testing
The testing phase involves automating testing as much as possible to ensure software quality and reduce manual labor.
Automated testing provides several key benefits that strengthen the reliability and efficiency of the software development process:
- Automated testing allows for early detection of issues or bugs
- It reduces manual effort and increases efficiency
- It ensures consistent and repeatable test results
- It speeds up feedback during development
- It improves test coverage compared to manual testing
Automated testing provides the fast, repeatable feedback teams need; the next step is to make these tests part of the integration process.
Integration
The integration phase builds automated testing by ensuring tests run automatically with each commit, seamlessly linking testing and integration to maintain code quality
The following points highlight key practices in the integration phase:
- Automate testing with each commit to the source code
- Allow for early detection of issues or bugs
- Reduce manual effort and increase efficiency
Once integrated changes have passed these automated checks, they can move forward to the deployment phase.
Deployment
The deployment phase is where we deploy our application into production. Considerations include:
- Application Configuration Management: Ensure that your application configuration is managed correctly
- Infrastructure as Code: Use infrastructure as code to manage your infrastructure
- Containerization: Use platforms like Kubernetes for containerization
Deployment makes the application available in production, but the work does not end...




