Audible Premium Plus

$14.95 a month

1 audiobook of your choice.
Stream or download thousands of included titles.
$14.95 a month after 30 day trial. Cancel anytime.
Buy for $6.95

Buy for $6.95

Pay using card ending in
By confirming your purchase, you agree to Audible's Conditions of Use and Amazon's Privacy Notice. Taxes where applicable.

Publisher's Summary

DevOps Handbook

If you are a tech, developer, part of a product management team or IT operator, then this audiobook is perfect for you in order to increase profitability, exceed productivity goals, and elevate work culture through DevOps methodology. You are aware of the fact that more than ever, the effective business management of technology is the most important and key towards successful business management, as well as business competitiveness. Another fact is that major technology leaders have greatly struggled in order to balance fundamental concepts such as security, reliability, agility, and consequences of failure, in fact, have never been greater. So if you want to know what the basic principles of the DevOps movement are and how to incorporate the DevOps concept and practices into your own organization, this audiobook will guide you through the world of the DevOps and through its main principles, so you can greatly increase organizational potential and reduce a risk of failure. Learn why all major organizations are adopting the DevOps methodology and follow their success story with DevOps.

What you will discover in this audiobook:

  • What are the benefits of DevOps
  • DevOps main goal and challenges
  • Explore guiding principles of DevOps
  • How to measure DevOps within your organization
  • Get to know what are continuous integration, continuous delivery, and continuous deployment
  • And much, much more.

Listen to this audiobook today and learn more about DevOps!

©2017 Christopher Weller (P)2017 Christopher Weller

What listeners say about DevOps Handbook

Average Customer Ratings
Overall
  • 4.5 out of 5 stars
  • 5 Stars
    33
  • 4 Stars
    3
  • 3 Stars
    5
  • 2 Stars
    0
  • 1 Stars
    0
Performance
  • 4.5 out of 5 stars
  • 5 Stars
    30
  • 4 Stars
    5
  • 3 Stars
    2
  • 2 Stars
    3
  • 1 Stars
    0
Story
  • 4.5 out of 5 stars
  • 5 Stars
    32
  • 4 Stars
    3
  • 3 Stars
    4
  • 2 Stars
    1
  • 1 Stars
    0

Reviews - Please select the tabs below to change the source of reviews.

Sort by:
Filter by:
  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

The source of DevOps.

DevOps is a relatively recent term that was presented at the Agile conference in 2008. Patrick Debois and Andrew Shafer presented this term on Agile infrastructure. The term was popularized through series of DevOps days that started in Belgium in 2009. Since the introduction, there have been various conferences worldwide on this subject. The popularity of DevOps practices and methodologies has been growing ever since especially in recent years. DevOps practices, in fact, have inspired many other initiatives such as WinOps, BizDevOps, and Ops Dev. DevOps really describes a certain approach to work rather than some distinct role such as system administrator. The need for an approach like DevOps arose from the great success of Agile software development which led to companies and organizations wanting to release software quicker and more frequently. They adopted some patterns like continuous integration tools, application release automation and continuous delivery, which are all fundamental, approaches of DevOps.

24 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

The must have DevOps handbook

Well, people tend to get rid of some unsatisfying parts that involve their job, so they are able to spend that additional time adding greater value to their organization, so at the end, everyone benefits greatly. Standardized production environment and automated deployments are, in fact, fundamental aspects of IT operations and DevOps models in general. It really makes various deployments more predictable so it frees people from frustrating routine tasks so they have greater freedom to dedicate to more creative and innovative tasks. DevOps is together operations and development, so we can say it is a clipped compound of these two disciplines. It supports delivery process, software development by monitoring and automating the process of integration, deployment, software testing, various infrastructure changes by establishing an environment where building new software, testing and releasing software can occur frequently, rapidly and with greater reliability.

21 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

For anyone in the DevOps field

DevOps term was introduced by Patrick Dubois in 2009. Patrick Dubois became DevOps chief proponent. As its name suggests, DevOps is simply operations and software development. These two disciplines were melded together in order to emphasize collaboration, communication, and 5 cohesion between IT operations teams and separate developer teams. The traditional approach looks at these two disciplines as two separated disciplines, but DevOps combines them together as one. A few years ago, major critical thinking on various converging methodologies including dynamics, thinking and systems which are part of Agile Operations Management, LEAN, Theory of Constraints and IT Service management started bubbling up in talks, various worldwide debates and the subjects were a major topic at various conferences. These conversations, in fact, are the main philosophy behind the DevOps tools and DevOps movement. DevOps methodology recognizes certain interdependence between two groups or two teams. Rather than seeing these teams as two independent groups, DevOps put them together to work together on their tasks. So these groups are not completely separated. By integrating functions like this one, one department of one team is organized to work on tasks. DevOps, in fact, helps a company or an organization to deploy their software more frequently and at the same time, it helps them to maintain their service stability. In this case gaining the speed is fundamental step towards better as well as more often innovations. In other words, everyone is able to provide and deliver the best results for their customers.

19 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

Fundamental

The DevOps fundamental concepts extend agile development techniques by further streamlining the movement involved in software change through deploy, validate, build and delivery stages. At the same time, it is empowering different cross-functionality teams with complete ownership of various software applications. These applications range from design to product support. DevOps also can be explained as an IT mindset, which encourages collaboration, communication, integration, and automation among different software developers and different IT operations in order to improve the overall speed and the overall quality of delivering software. DevOps teams including developers and operators really focus on better standardizing development environments as well as on automating different delivery processes in order to improve delivery security, efficiency, predictability, and maintainability. The DevOps provide more control to developers so they control the production environments and at the same time, they had better understand the overall production infrastructure. DevOps also encourages empowering different teams with greater autonomy to validate, deliver, build and support their applications.

18 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

Good advice on IT devops

There have been many books written about DevOps, agile, disruption and technology driven business transformation, but there are few that are so easy to read, concise and yet consumable. DevOps on its own is a pretty dry subject, but the author injects humour, many customer stories, and simple (often sporting) analogies to explain a whole range of concepts. It is a well thought through, and logical approach to explaining where to start, how to adopt DevOps, and overcoming the barriers to adoption.

12 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

Comprehensive and Actionable Overview

DevOps recently has become an overloaded buzzword, which means many different things to many different people. That is the greatest challenge when it comes to the understanding DevOps better. Instead of trying to define this discipline, it is better to describe its fundamental concept. History of this movement will also serve well so you can better understand these concepts and you will get a holistic view. Google introduced site reliability engineering in 2003. This is a new approach which features some continuous into large-scale as well as high-availability systems while are the same time it maintains high-quality customer experience. While site reliability engineering, in fact, predates the development of DevOps, these two are generally considered as independent trends. However, DevOps have taken some aspects of site reliability engineering as well. DevOps is often considered as an approach, which helps system administration work to in continuously advancing, could technology.

11 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

Set the right path

DevOps oversees some shared services and promotes the use of various development tools and some of the best available practices. When it comes to the enterprise, traditionally team is involved in developing and testing new codes in a completely isolated environment for better quality assurance. In a case when requirements were met, they release that code to various operations for further use. The team, which is involved in operations, will deploy that program and maintain it further. From that point, the code is released. The main problem with this particular approach is common waterfall development. Waterfall development can be 3 described as a long time between particular software releases. This frequently happens when there are two teams involved but they work in separate environments. In fact, the team which is involved in development can’t be always aware of specific operational roadblocks which might prevent their specific program from working properly. It may happen often that the program is not working as previously anticipated.

9 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

Make my work tasks easier

Services and software is available across multiple platforms. The book gives a very good overview on devops and is well written.

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

DevOps for the People

A lot of good messages and insights we have in this book mainly for those responsible to manage and deliver the DevOps adoption in the companies.

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars

Great for any IT person

There are some fundamental goals when it comes to the DevOps practices. One of the main goals is to improve collaboration between stakeholders from the very beginning that includes planning through delivery as well as automation. According to the research from 2015, DevOps deploy thirty times more frequently with two hundred times shorter lead times and it provides sixty times fewer failures and recovers hundred sixty-eight times faster as well.

Sort by:
Filter by:
  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for  Derek
  • Derek
  • 07-18-20

A Great How To Guide!

Before the introduction of the DevOps practices, teams were mainly in charge of obtaining various business requirements for writing code and software programs. Further separate quality assurance team tests the program in some isolated development environment. In the case when all of the requirements were met, the code is released for further operations to deploy. On the other hand, the deployment teams are further fragmented into groups like database and networking. Each time a software program is let’s say thrown over the wall or deployed, and the independent team adds bottlenecks. The problem with this approach is that when teams like development and quality teams work completely independently are various.

24 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for Nicole  Dunigan
  • Nicole Dunigan
  • 07-20-20

DevOps along for the ride

DevOps is really more than just a tool and it is more than a process change. It in fact inherently requires certain culture shift. This cultural change is difficult since it conflicts nature of fundamental roles, which are operations, developers, and testers. Operations seek overall organizational stability while developers seek that change. On the other hand, testers seek to reduce overall risks. One of the greatest challenges when it comes to the DevOps enterprise is in fact how to get these three groups to collaborate and work cohesively. DevOps reflects some complex topic, while its community uses various analogies in order to communicate fundamental and relevant concepts. DevOps fundamental principles, in fact, demand very strong interdepartmental collaboration and communication. It means it demands teams that work together while building and engaging in other employee activities. DevOps principles demand environments, which fosters both cultural change and communication between teams within an organization. Team-building activities include various trust activities as well as workers engagement seminars.

21 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for  Andrew Miura
  • Andrew Miura
  • 07-21-20

If you buy one book on devops, make it this one

At the very beginning, agile teams were mostly made up of developers. Since these teams made up of developers became more efficient and effective at software development, it was clear that having development and quality assurance as two separate teams were greatly inefficient. Further agile grew up in order to encompass quality assurance in order to increase the overall velocity of delivering software. Agile then grow up to encompass support and delivery members to extend the overall agility from specific ideation to delivery. Continuous delivery and DevOps, in fact, have many common goals so they are frequently used in conjunction. However, there are some differences as well. Continuous delivery is mainly focused on automating software delivery processes. However, DevOps also focuses on the company and organization change in order to support better collaboration between various functions, which are involved. Therefore, continuous delivery and DevOps share the same background in lead thinking and agile techniques. Both are focused on small but quick changes and on a value that would be presented to end-customer. They are also well collaborated and communicated internally, which is helpful when it comes to the achieving fast time to market with greatly reduced risks.

17 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for Tegan
  • Tegan
  • 07-26-20

GET THIS BOOK!!!

I've taken a keen interest in the evolution of software delivery practices over the last couple of decades, and have experienced the transition from traditional to iterative to agile to scaled agile to devops approaches, both as an employee and consultant to other organizations. There are dozens of books on DevOps. There are however very few that are a focussed, practical guidebook on how to adopt and scale DevOps in a large enterprise. The author looks at both what practitioners need to do to succeed with DevOps adoption, and what the enterprise's leadership needs to do.

15 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for Cynthia Johnson
  • Cynthia Johnson
  • 07-29-20

A must for every IT professional!!

Simple processes with DevOps practices become more dynamic and programmable. DevOps, in fact, aims to maximize the efficiency, predictability, maintainability, and security of operational processes. Commonly automation supports all of these objectives. DevOps integration really targets continuous testing, product delivery, quality testing and various feature development as well as maintenance releases to improve security and reliability and to provide quicker developments and deployments. Many of the DevOps in fact, came from already mentioned agile software development and enterprise systems management. DevOps helps to various software applications and organizations’ release management by factoring their infrastructure, which is related to code. When you combine version control, ticket tracking system and configuration management tool, changes will be faster and easily processed as well as tracked and reported. Development and operation teams have a great interest as well as a stake in keeping the overall production up and continuously running. In other words, any code which is related to the infrastructure is considered as another artifact in the overall software delivery process.

11 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for Ronal
  • Ronal
  • 08-02-20

DevOps: not easy but worthwhile

Contains great intro material for novices or the many folks who have received a barrage of conflicting definitions of DevOps. This audiobook will guide you through the world of the DevOps and through its main principles, so you can greatly increase organizational potential and reduce a risk of failure. If you are embarking on a transformation journey in your business, DevOps is likely to be part of it, and this guide will certainly give you 'food for thought', but hopefully a whole lot more.

7 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for Efren Bright
  • Efren Bright
  • 08-08-20

The definitive guide to DevOps

Continuous integration, in fact, saves a lot of time when the development team is ready to release their code. Continuous integration isn't DevOps's term but an agile engineering practice which is originating from the Extreme Programming methodology. These terms are around for a while. The DevOps in fact adopted this term since automation is required in order to successfully execute continuous integration. It is in fact commonly the first step towards DevOps maturity. The continuous integration when it comes to the DevOps involves checking your code and further compiling it into binary executable and usable code in order to run fundamental validation testing.

3 people found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for  Holmes
  • Holmes
  • 08-06-20

Like seeing your IT department through a reality

Like seeing your IT department through a reality mirror. This book is step by step guide into the world of DevOps. Before we get into the subject much deeper, we will briefly discuss what DevOps is and how we can use it in a great variety of practices. DevOps is a certain combination that includes tools, some cultural philosophies, and practices. These combinations are used in order to increase a company’s as well as organization’s ability to deliver specific services and applications at high velocity. In fact, DevOps makes possible for companies to evolve and improve their products at much faster pace than those organizations and companies which use traditional infrastructure management and traditional software development. This greater speed enables these organizations to better serve and compete more effectively in the overall market. DevOps, in fact, is the blending of various tasks, which are performed by company’s application development as well as system operations teams. This term may be used in a different way but the meaning remains the same. In broad meaning, it is an operational philosophy, which promotes greater communication between various development systems, and operations since a greater number of elements become programmable. If we put it in another most narrow interpretation, we can say that DevOps, in fact, describes the part of a company’s tech team or IT team which maintains and creates company’s infrastructure. This term also can be used in order to describe a culture, which strategically looks at software delivery chain.

1 person found this helpful

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for Jackson
  • Jackson
  • 08-09-20

Impress Book

Christopher has clearly a large experience on the subject and this course is right what I have been looking for: transforming from ITIL to Devops with a focus on production teams. Thank you!

  • Overall
    5 out of 5 stars
  • Performance
    5 out of 5 stars
  • Story
    5 out of 5 stars
Profile Image for James
  • James
  • 08-08-20

The missing IT guide.

DevOps is together operations and development, so we can say it is a clipped compound of these two disciplines. It supports delivery process, software development by monitoring and automating the process of integration, deployment, software testing, various infrastructure changes by establishing an environment where building new software, testing and releasing software can occur frequently, rapidly and with greater reliability.