What do you think?
Rate this book
Continuous delivery and DevOps A Quickstart Guide
For a while now, there has been a buzz around the IT industry regarding continuous delivery and DevOps. This book will provide you with some background information into these two new kids on the block and how they can help you to optimize, streamline and improve the way you work and ultimately how you ship quality software.
"Continuous delivery and DevOps: A Quickstart guide" will provide you with a clear and concise insight into what continuous delivery and DevOps are all about, how to go about preparing for and implementing them and what quantifiable business value they bring. Included within are some tricks and trips based upon real world experiences which may help you reduce the time and effort needed if you were to go it alone.
"Continuous delivery and DevOps: A Quickstart guide" will provide you with a clear and concise insight into what continuous delivery and DevOps are all about, how to go about preparing for and implementing them and what quantifiable business value they bring. Included within are some tricks and trips based upon real world experiences which may help you reduce the time and effort needed if you were to go it alone.
154 pages, Paperback
First published November 1, 2012
15 people are currently reading
198 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 11 of 11 reviews
April 15, 2015
Hmm. I think one of those books that is hard to fault for what it does say, but suffers from attempting to throw too wide a net without following through with the hard work necessary to haul in such a large catch.
i.e. it is a bit of a scatter gun of little nuggets across the entire delivery and operations scene, but doesn't go deep into anything.
Technologists of any reasonable experience won't find it useful. You might find initial ideas here, but will need to go elsewhere for the details needed to execute.
So a technical reader will concluded this must be a book for "Executives". But if that's you, I think you may also be dissatisfied... because for you it is too detailed, and lacks a clear message and bullet points pulling it all together. If the book was 200 pages shorter, maybe..
i.e. it is a bit of a scatter gun of little nuggets across the entire delivery and operations scene, but doesn't go deep into anything.
Technologists of any reasonable experience won't find it useful. You might find initial ideas here, but will need to go elsewhere for the details needed to execute.
So a technical reader will concluded this must be a book for "Executives". But if that's you, I think you may also be dissatisfied... because for you it is too detailed, and lacks a clear message and bullet points pulling it all together. If the book was 200 pages shorter, maybe..
June 15, 2015
Very conceptual, there is not specific tools, only methods and concepts.
Maybe is a good start for some managers, or some stakeholders. Contains a good philosophy and the analogies are clear. In some chapters I had to hold the reading because are long and if you left it maybe should to read from the beginning.
In brief: the point is reached but maybe could be more concise.
Maybe is a good start for some managers, or some stakeholders. Contains a good philosophy and the analogies are clear. In some chapters I had to hold the reading because are long and if you left it maybe should to read from the beginning.
In brief: the point is reached but maybe could be more concise.
September 19, 2013
This book is really for managers or non technical people.
There's a lot of explanation about what are the activities around CD and Devops, but nothing that worth to a technical person.
There's a lot of explanation about what are the activities around CD and Devops, but nothing that worth to a technical person.
May 23, 2020
As the name states, this is just a "quickstart" and is a rather good one for a reader that wants to layout foundations of what "continuous integration" and "DevOps" entitles. Not recommended for someone who already has some experience on the topic. But otherwise, it is easy to follow and provides punctual takeaways that you can either find as a simile with your organization or action points to improve it.
Serves as an entry point into the topic.
Serves as an entry point into the topic.
August 31, 2017
Tried a little too hard to be liked. Still, if you are new to DevOps and want to read something to learn about it, it gets the job done.
April 14, 2015
If you have got your hands on this book thinking to find something technical about automation and software engineering or the best practices acknowledged by the DevOps community, sadly, you will get disappointed. Get the book back to the shelf if you still can. Sit down, breath deep and get ready for a disappointing read otherwise. This evangelical title tells us the story of three employees of an imaginary company, ACME and how they got both enlightenment and success by embracing the DevOps side.
When I see a book about continuous integration/delivery and DevOps I do expect to find something related to automation. I demand chapters dedicated to the different tools that help a team to continuously deliver code to production minimizing the risks, such as Jenkins or BuildBot. I want pages dedicated to either Chef or Puppet. Ansible doesn’t bother me either. Docker would be ice on the cake.
Unfortunately this book does not provide anything technical. Not a single line. Disappointing but fine, there are texts dedicated to non IT people, those of the Business department or the boss himself. These people do not need to see code. They must be shown graphs and numbers that prove them the costs involved in moving towards the light (DevOps), and the risks that come with it.
Such a book should definitely present some real case, the story of a couple of startups that, by embracing the DevOps philosophy, were able to avoid problems delivering software to the clients, despite the demand kept increasing over and over. And how all of this led these companies to climb the ladder up into wealthiness. Again, you will not find anything like this in this title. Not a single graph, not any real world successful story.
This book tells the story of these three employees of this imaginary company and how they pass from disregarding each others feeling to love, success and DevOps. It’s a purely theoretical title that tries to convince you to take a leap of faith and love the movement.
Recommended? Not really. Very disappointing title.
As usual, you can find more reviews on my personal blog: http://books.lostinmalloc.com Feel free to pass by and share your thoughts!
When I see a book about continuous integration/delivery and DevOps I do expect to find something related to automation. I demand chapters dedicated to the different tools that help a team to continuously deliver code to production minimizing the risks, such as Jenkins or BuildBot. I want pages dedicated to either Chef or Puppet. Ansible doesn’t bother me either. Docker would be ice on the cake.
Unfortunately this book does not provide anything technical. Not a single line. Disappointing but fine, there are texts dedicated to non IT people, those of the Business department or the boss himself. These people do not need to see code. They must be shown graphs and numbers that prove them the costs involved in moving towards the light (DevOps), and the risks that come with it.
Such a book should definitely present some real case, the story of a couple of startups that, by embracing the DevOps philosophy, were able to avoid problems delivering software to the clients, despite the demand kept increasing over and over. And how all of this led these companies to climb the ladder up into wealthiness. Again, you will not find anything like this in this title. Not a single graph, not any real world successful story.
This book tells the story of these three employees of this imaginary company and how they pass from disregarding each others feeling to love, success and DevOps. It’s a purely theoretical title that tries to convince you to take a leap of faith and love the movement.
Recommended? Not really. Very disappointing title.
As usual, you can find more reviews on my personal blog: http://books.lostinmalloc.com Feel free to pass by and share your thoughts!
March 22, 2015
It turned out this was mostly a book about soft skills, with technical topics not being in the forefront. There were a couple of tools mentioned, and the importance of monitoring and metrics was strongly pointed out, but I expected more than that. I might be a bit biased due to my engineering background, though.
A common thread through all the chapters is a story about a fictional company which successfully implemented DevOps. It serves as an example of the journey and the practices involved. Probably the most important message it tries to get across, is the fact that there's no such thing as DevOps in a box: you can't buy it or just hire an expert - everyone needs to live it and breathe it.
In the end the book falls a bit short and remains just an overview of methodologies and approaches, with lots of pointers to further resources. Although, not really actionable on its own, it is still a good starting point to learn about DevOps: what it is and why you might want to take on the task of implementing it.
A common thread through all the chapters is a story about a fictional company which successfully implemented DevOps. It serves as an example of the journey and the practices involved. Probably the most important message it tries to get across, is the fact that there's no such thing as DevOps in a box: you can't buy it or just hire an expert - everyone needs to live it and breathe it.
In the end the book falls a bit short and remains just an overview of methodologies and approaches, with lots of pointers to further resources. Although, not really actionable on its own, it is still a good starting point to learn about DevOps: what it is and why you might want to take on the task of implementing it.
May 10, 2013
It needs quite some editing, but I heard that a lot of Packt books are like that. Not a big deal for me.
It is mostly oriented towards managers and people who want to get their feet wet with "this whole DevOps thing". Don't expect code, advanced techniques or tools, but that's not necessarily a bad thing. It covers a lot of the soft processes and cultural changes needed to implement DevOps and continuous delivery.
Good quick read overall.
It is mostly oriented towards managers and people who want to get their feet wet with "this whole DevOps thing". Don't expect code, advanced techniques or tools, but that's not necessarily a bad thing. It covers a lot of the soft processes and cultural changes needed to implement DevOps and continuous delivery.
Good quick read overall.
June 11, 2015
I'm going to gentler than other reviewers.
This is the book to give to non-technical managers, or leary sys admins, or project managers.
If you want technical, read Jez Humble and Dave Farley's book. If you want a mostly high-level intro/overview, read this book.
This book is easy to read and has some good visual aspects.
This is the book to give to non-technical managers, or leary sys admins, or project managers.
If you want technical, read Jez Humble and Dave Farley's book. If you want a mostly high-level intro/overview, read this book.
This book is easy to read and has some good visual aspects.
Read
April 6, 2015good as a quick start. but nothing more that that.
Displaying 1 - 11 of 11 reviews