Learning DevOps: A comprehensive guide to accelerating DevOps culture adoption with Terraform, Azure DevOps, Kubernetes, and Jenkins, 2nd Edition

This book is worth a read for any beginner who plan on using Azure to deploy their web applications. Through it, you will learn a lot of basic things such as using Git but also get a good introduction to some more advanced DevOps topics and tools. I particularly liked the fact that this book closes the "DevOps feedback loop" by showing you practical ways to test your code such that you can build and run a CI/CD pipeline with minimal downtime

If you have ever thought of learning about DevOps, how to create a DevOps cultural mindset and how to implement the IT infrastructure you need. This is the book for you. Also, if you want to learn about MLOps, this is a great starting point. Kudos Mikael for a great second edition to the book.

This book would get five starts, except that for some reason, the text is gray when you make the background black. You cannot change the font color, either. Why? This is terrible. The contrast is horrid.

OverviewRecently, I was contacted by Packt Publishing to do a review for a new book called Learning DevOps. Learning DevOps is a rather comprehensive book (it's over 500 pages!) on DevOps culture and practice. Most everything that an engineer might want to know about DevOps is at least touched on here. The book starts with the basics of providing a definitional understanding of DevOps concepts, and eventually moves on to cover application of DevOps through specific tools that are commonly used day to day.First ImpressionsInitially, I found the book to be very thorough in its explanation of what DevOps is. Often I think people are confused about DevOps because in many organizations is a title held by an engineer with a certain set of responsibilities. But this isn't really what DevOps is. It's not so much a specific job description as it is a culture. Oftentimes people within an organization may be called DevOps Engineers, while the organization is not exactly following DevOps principles at all.While explanations are thorough, there are at times places that the terminology used can be confusing. One such example is in the discussion about Continuous Delivery where tools like Nexus and ProGet are referred to as package managers. Usually, a package manager would be something like apt or npm, which manages local installation of packages for a specific platform, where I would consider something like Nexus or ProGet to be referred to as package repositories or artifact repositories.ContentI found section one mostly to be documentation on setting up the basic tools of the DevOps practitioner, such as Ansible and Terraform. While it may be helpful for the absolute beginner, I found it to be a bit verbose at times, and incorporating a lot of things that could easily be looked up in the tool's own documentation.Section two I found to be useful for those who haven't used version control in the past. Of course, this goes again with the theme of the absolute beginner. Section three was similar in that it was a rather brief overview of what I think is one of the most important topics for the modern DevOps practitioner. Kubernetes is being used by more and more companies now, and more depth on this section could have been interesting. Still, it was a good introduction.Section four was actually quite interesting. Using Postman and Newman for testing APIs was a rather novel but useful idea. I was also really impressed that the author covered application security and incorporating that into DevOps. I think this is still an idea that hasn't spread as much as it should. DevSecOps really should be the future for software companies as more regularly we see security flaws and breaches in the wild. The final section of the book expanded even further on security and that was nice to see. This was really the best part of the book for me and nice to see in an introductory text.SummaryOverall I thought that Learning DevOps was a clear introduction to DevOps and the tools of the trade, though at times it could be verbose. I would certainly recommend the book to anyone who is being thrown into a position where they need to get up to speed on DevOps quickly. It provides all the basics in one place and can act as a useful reference.

The problem with books about DevOps is that they typically deep dive in the trenches of DevOps technology right from the start. But, DevOps in the first place is about culture, it’s a mindshift. A mindshift to the left, granting teams to take more responsibility on how they develop and operate products. That comes with trust and trust is a matter of culture.In all honesty, reading the subtitel of this book, made me worry a bit. Reading words such as Terraform, Kubernetes, Jenkins and Azure DevOps does give the impression that is very much a tech-book for developers - although culture adoption is mentioned as well in the title. Mikael Krief rightfully starts with this: the cultural aspects of DevOps. But let there be no mistake: this is a tech-book, going through every aspect of Infrastructure as Code, configuration as code, CI/CD pipelines, containers and container orchestration with Kubernetes.The first three sections is a deep dive in the industry leading tooling, starting with Terraform to deploy infrastructure to Azure. (Be aware that this book focuses on the usage in Azure.) Next, we get into Ansible to configure the infrastructure and Packer to optimize the infra. The second section is about setting up the CI/CD pipelines, using Git, Jenkins and Azure DevOps. Logically, this section is followed by an extensive guide on how to work with Docker containers and Kubernetes container orchestration. Since the book focuses on Azure, obviously there's quite some detailing on using Helm charts with ACR and AKS.Again, the author gets me worried a bit at this stage. DevOps is a shift-left movement, so where's the security and specially the testing of the code? Test-driven development is likely one of the most important aspects in DevOps and luckily the whole of section 4 is about testing the application, security and performance tests. In the final chapter, best practices are listed, including the shift-left in security.In short: this is probably one of the most complete books on DevOps targeting the Azure cloud. In well over 500 pages every aspect of DevOps is discussed. The only 'downside' is that by trying to be as complete as the author, topics tend to just start scratching the surface. But overall: this is a very good, yet technical introduction to learn about DevOps.

Very nice product covering all the concepts

Cette seconde édition vaut le détour !L’auteur est vraiment incollable sur le sujet

I like the cobtent of this book. it is vast and good for those who has some knowledge on DevOps. Only problem was I had to replace it with a wrong book earlier. Amazon had delivered a wrong book in my furst order. For that reason I was handed it over after 15 days of my order date

Dans le cadre du travail.