Practical DevOps: Harness the power of DevOps to boost your skill set and make your IT organization perform better

Nicely written book. I shared it with my DevOps class

Quality book.

This book provides an insightful overview of how to get started with DevOps.The author makes the specific components of DevOps understandable and easily accessible both for developers and operations. The book is littered with examples and practical solutions to real world problems.The book nicely summarised all the aspects of the field of DevOps. It was an easy read and I highly recommended for anyone whose interested in DevOps.This book is an excellent primer in the field!

This book is a real eye-opener. I've been an IT professional for longer than I'd care to admit, most recently working outside the IT function - but engaged closely with IT colleagues - in a large business with complex internal and outsourced development and likewise infrastructure. While I recognise the philosophy/approach described in the book, I'd never come across most of the specific tools or appreciated how they can provide the sort of integrated approach described here. The book is high-level enough to explain the approach, interleaved with how-tos and examples that would give a flying start on actually implementing. Highly recommended.

Hi,I have written a detailed chapter-by-chapter review of this book on www DOT i-programmer DOT info, the first and last parts of this review are given here. For my review of all chapters, search i-programmer DOT info for STIRK together with the book's title.This book aims to provide an introduction to DevOps from a practical perspective, how does it fare?DevOps is a skill increasingly in demand, it’s purpose is ‘...to make faster, more correct releases by bringing people working with different disciplines closer together.’The book is aimed at developers and system administrators. While no previous knowledge of DevOps is required, some background knowledge of Agile, Scrum, Kanban, Puppet etc is needed to get the most out of the book. It contains 210 working pages, spread over 10 chapters.Below is a chapter-by-chapter exploration of the topics covered.Chapter 1 Introduction to DevOps and Continuous DeliveryThe book opens with some history about DevOps, being a combination of the words ‘development’ and ‘operation’, it’s concerned with removing the wall between the two. It overlaps with Agile, automation and continuous delivery. The importance of communication, shared tools, cooperation between roles, and the meaning of waiting is discussed (waiting suggests something is wrong).The chapter continues with a look at the different cycles within Agile, including Scrum, and Kanban, explaining DevOps supports all cycles, and encourages cooperation between groups. Some examples of how DevOps benefits Agile cycles are given (e.g. faster regular deployments). The importance of doing Agile/DevOps for improved measurable results rather than just following the steps (i.e. cargo cults), is noted. DevOps aims to make interaction with new systems faster and easier, for everyone.The chapter ends with a brief look at how DevOps interacts with other ways of working. Typically, Agile or Lean frameworks work well with DevOps (since it came from Agile), however ITIL sometimes has problems, since it can be viewed as less flexible.This chapter provides a useful background about what DevOps is, where it came from, and how it interacts with other frameworks. The emphasis on interaction and communication is noted.The chapter is easy to read, well written, with useful diagrams, and helpful links to other chapters. It’s apparent that some knowledge of Agile, Scrum, Kanban, Puppet etc is needed to get the most out of the book. Perhaps these terms should have been defined here to ensure all reader are at the same level? I note Kanban is described in chapter 9. These traits apply to the whole of the book....ConclusionThis book aims to provide an introduction to DevOps from a practical perspective, and succeeds. The book is generally easy to read, well written, with useful diagrams, and helpful links to other chapters. The place of DevOps in the various stages of the Continuous Delivery pipeline is described well, and there are plenty of practical example problems and suggested solutions.It’s apparent that some background knowledge of Agile, Scrum, Kanban, Puppet etc is needed to get the most out of the book. It would have been useful to have defined some of these basic terms in Chapter 1, to ensure all readers are at the same assumed level of understanding.Some chapters, for example Chapter 3, have areas that aren’t cohesive, with subsections appearing without sufficient context or linkage.If you come from a Windows development/admin background you can expect a few more problems reading the text than if you’re from a Unix/Java background.Overall, this is a useful introduction and overview to DevOps.