The DevOps Toolkit Series Are Born

The DevOps 2.1 ToolkitAt the beginning of 2016, I published The DevOps 2.0 Toolkit. It took me a long time to finish it. Much longer than I imagined.

I started by writing blog posts in They become popular and I received a lot of feedback. Through them, I clarified the idea behind the book. The goal was to provide a guide for those who want to implement DevOps practices and tools. At the same time, I did not want to write a material usable to any situation. I wanted to concentrate only on people that truly want to implement the latest and greatest practices. I hoped to make it go beyond the “traditional” DevOps. I wished to show that the DevOps movement matured and evolved over the years and that we needed a new name. A reset from the way DevOps is implemented in some organizations. Hence the name, The DevOps 2.0 Toolkit.

As any author will tell you, technical books based mostly on hands-on material do not have a long time span. Technology changes ever so quickly and we can expect tools and practices that are valid today to become obsolete a couple of years afterward. I expected The DevOps 2.0 Toolkit to be a reference for two to three years (not more). After all, how much can things change in one year? Well, Docker proved me wrong. A lot changed in only six months since I made the book public. The new Swarm was released. It is now part of Docker Engine v1.12+. Service discovery is bundled inside it. Networking was greatly improved with load balancing and routing mesh. The list can go on for a while. The release 1.12 is, in my opinion, the most significant release since the first version that went public.

I remember the days I spent together with Docker engineers in Seattle during DockerCon 2016. Instead attending the public sessions, I spent four days with them going through the features that will be released in version 1.12 and the roadmap beyond it. I felt I understood all the technical concepts and features behind them. However, a week later, when I went back home and started “playing” with the new Docker Swarm Mode, I realized that my brain was still wired to the way the things were working before. Too many things changed. Too many new possibilities emerged. It took a couple of weeks until my brain reset. Only then I felt I truly understood the scope of changes they introduced in a single release. It was massive.

In parallel with my discovery of the Swarm Mode, I continued receiving emails from The DevOps 2.0 Toolkit readers. They wanted more. They wanted me to cover new topics as well as to go deeper into those already explored. One particular request was repeated over and over. “I want you to go deeper into clustering.” Readers wanted to know in more detail how to operate a cluster and how to combine it with continuous deployment. They requested that I explore alternative methods for zero-downtime deployments, how to monitor the system more efficiently, how to get closer to self-healing systems, and so on. The range of topics they wanted me to cover was massive, and they wanted it as soon as possible.

Hence, I decided to start a new book and combine my amazement with Docker 1.12 with some of the requests from the readers. This time, I did not want to wait for a year until the book is published but pick a smaller scope and release it as soon as possible. Hence, The DevOps 2.1 Toolkit is born. More importantly, The DevOps Toolkit Series came into existence.

This time, the publishing process will be leaner than before. Today I published the first 60 pages of the book hoping that people will pick it up this early. I’m expecting your feedback. Tell me what you like and dislike, let me know if I made a mistake, influence the direction I’m taking. Is there a chapter you’d like me to cover in more details? Is your favorite hosting provided included? Do you think that a different process or a tool should be used? Please send me your feedback to my email, Skype, or HangOuts (info is in the About section of this blog).

I created a special coupon with 50% discount for the first 25 readers. Please use to claim it.


3 thoughts on “The DevOps Toolkit Series Are Born

  1. Ingemar Erling

    Hi Viktor,
    I am reading your book, “The DevOps 2.1 Toolkit: Docker Swarm” (2018-12-14) and my goal is to understand CI and CD , CDP – publishing docker images to my docket-hub account and fetching them to the test-machine and prod-machine. And then learning all the unknowns in the process.
    I get a bit puzzled about the discussion about the Docker-machine, so I really need that? I am running on Linux today and using Docker and “docker compose”
    Where out gets confusing with me is here
    “Machine was the only way to run Docker on Mac or Windows previous to Docker v1.12. Starting with the beta program and Docker v1.12, Docker for Mac and Docker for Windows are available as native apps and the better choice for this use case on newer desktops and laptops.”
    Could you give me some advice before continue to read?

    Best, ingo

  2. Viktor Farcic Post author

    Docker Machine has been deprecated since I published that book. Use Docker For Desktop (Mac or Windows) instead. On top of that, remember that it is useful only for local purposes when you want to run something on your laptop. For anything more serious (e.g., CI/CD/CDP), you’ll need a “real” cluster. For Docker Swarm, I suggest Docker For AWS/Azure. If you plan to run it somewhere else, creating your own cluster should be straightforward.

    Please let me know if that answers your question.

  3. Ingemar Erling

    Thank you for that answer Victor!
    then I will keep on reading the book but leave out the docker-machine part – still hope that the CI/CD/CDP -parts will give me a good understanding of the required process during the holidays.
    We are now running on our own Linux-machines, we will be doing so, and not yet in a cluster – but that might change in the future

    best, i


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s