Book Review: The DevOps Handbook
Before read this book, I thought DevOps simply means a person who can do development and system maintenance, the result is how terribly wrong I am, DevOps’ target is make developer and operations cooperate perfectly:
DevOps (a clipped compound of “development” and “operations”) is a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). The main characteristic of the DevOps movement is to strongly advocate automation and monitoring at all steps of software construction, from integration, testing, releasing to deployment and infrastructure management. DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases, in close alignment with business objectives.

A simple introduction to DevOps:
The need for DevOps arose from the increasing success of agile software development, as that led to organizations wanting to release their software faster and more frequently. As they sought to overcome the strain this put on their release management processes, they had to adopt patterns such as application release automation, continuous integration tools, and continuous delivery.
Agile is a really good concept, DevOps also is a very good guideline, make me remind a video talk about Spotify mode, all these things can combine together to make a work flow smoothly and effectively:
