Unlocking DevOps 2.0: Key Insights from the ‘Black Treasure’ Book

Book Overview

DevOps 2.0 Toolset is a dense 396‑page book that presents a comprehensive guide to automating continuous‑delivery pipelines using containerized micro‑services. The author, Viktor Farcic, a senior consultant at CloudBees, shares practical experience from both green‑field projects and legacy system integrations.

Chapter Structure

The book is organized into the following chapters:

DevOps concepts

Practical breakthroughs: continuous delivery, micro‑services and containers

System architecture

Configuring development environments with Vagrant and Docker

Deploy pipeline – initialization phase

Configuration management in the Docker world

Deploy pipeline – middle phase

Service discovery: the key to distributed services

Proxy services

Deploy pipeline – final phase

Automating the deployment pipeline

CI/CD tools

Blue‑green deployment

Cluster and service scaling

Self‑healing systems

Centralized logging and monitoring

Key Insights from Chapter 1: DevOps Concepts

The author contrasts two project types: new green‑field developments that can adopt the latest languages and stacks, and legacy extensions that must integrate with existing systems, often using waterfall processes. He argues that green‑field projects benefit from rapid iteration and low‑cost redesign, while legacy projects suffer from high integration costs and limited innovation.

Traditional development places system integration testing at the end, leading to costly rework. From these experiences the author emphasizes the necessity of CI/CD, noting that although CI/CD is often seen as an Ops responsibility, developers must also adopt automation tools to avoid accumulating technical debt.

Effective CI/CD requires fast feedback loops—down to minutes—and must involve every stage from architecture design to testing, ensuring both business and management requirements are met. The author stresses holistic, systemic thinking.

He uses an analogy: refactoring a monolithic, tightly‑coupled legacy application is like trying to turn an eighty‑year‑old woman into a young girl—extremely difficult. Micro‑services, by contrast, consist of many small, independently maintained services that can be written in any language or framework without affecting others, and can be deployed independently. The key is sensible service boundaries rather than arbitrary size.

The author warns against tightly‑coupled shared libraries and overly standardized interfaces, which can become hidden obstacles to innovation.

Deployment challenges are highlighted: binaries (JAR, WAR, DLL) must be deployed across heterogeneous environments. Virtual machines provide consistency but introduce configuration drift over time. Immutable servers are advocated, yet existing tools often lack full support for true immutability.

Traditional configuration management tools such as Puppet and Chef, when used without systematic thinking, become a nightmare. The author proposes a “dream toolset” consisting of: Ansible – as a replacement for Puppet and Chef. Docker – to replace slow virtual machines and enable immutable deployments.

Service discovery platforms – using Swarm, Kubernetes, or Mesos/DCOS.

Additional tools mentioned for large‑scale micro‑service architectures include CoreOS, etcd, Consul, Fleet, Mesos, Rocket, among others.

Conclusion

The chapter ends with a strong endorsement of the presented toolset and a call to readers to experiment with the book’s sample code to truly master the concepts.