The DevOps 2.0 Toolkit

The DevOps 2.0 Toolkit

Today is an exciting day for me. I just decided that the book I spent the last eight months writing is ready for general public.

What made me write the book? Certainly not the promise of wealth since, as any author of technical books will confirm, there is no money that can compensate the number of hours involved in writing a technical book. The reasons behind this endeavor are of a different nature. I realized that this blog is a great way for me to explore different subjects and share my experience with the community. However, due to the format, blog posts do not give enough space to explore, in more details, subjects I’m passionate about so, around eight months ago, I decided to start working on The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices book. It treats similar subjects as those I write about in this blog, but with much more details. More importantly, the book allowed me to organize my experience into a much more coherent story.

The book is about different techniques that help us architect software in a better and more efficient way with microservices packed as immutable containers, tested and deployed continuously to servers that are automatically provisioned with configuration management tools. It’s about fast, reliable and continuous deployments with zero-downtime and ability to roll-back. It’s about scaling to any number of servers, designing self-healing systems capable of recuperation from both hardware and software failures and about centralized logging and monitoring of the cluster.

In other words, this book envelops the whole microservices development and deployment lifecycle using some of the latest and greatest practices and tools. We’ll use Docker, Kubernetes, Ansible, Ubuntu, Docker Swarm and Docker Compose, Consul, etcd, Registrator, confd, Jenkins, and so on. We’ll go through many practices and, even more, tools.

At this moment, around 70% is finished and you’ll receive regular updates if you decide to purchase the book. The truth is that my motivation for writing the book is the same as with this blog. I like sharing my experience and this book is one more way to accomplish that.

Please give The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices a try and let me know what you think. Any feedback is welcome and appreciated.

Have the book in front of me. Very promising and detailed read.

Like
Reply

Does it provide any information why DevOps 1.0 was failing?

Like
Reply

Bought your book! Very nice read!

Like
Reply

To view or add a comment, sign in

More articles by Viktor Farcic

  • Do Shared Services Teams Break The DevOps Rules?

    We discussed it in the latest episode of DevOps Paradox. I'd love to hear your comments.

  • Best DevOps Book/eBook of the Year

    I'm very excited that DevOps Paradox (https://amzn.to/2myrYYA) is one of the "DevOps Dozen Finalists" https://devops.

  • Are you a hacker or a developer?

    Did you ever wonder what is the difference between hackers and developers within your company?…

  • DevOps Paradox Giveaway

    DevOps Paradox (the book, not the podcast) is finished: https://www.packtpub.

    14 Comments
  • DOP 18: How To Avoid Issue Tracking Mistakes Teams Make

    In the latest episode of The DevOps Paradox Darin and I tried to answer Neil's question. "What is the best way to track…

  • Call for questions

    The "call for questions" podcast episode in https://www.devopsparadox.

  • Elasticity and Scalability Are the Keys

    A short while ago beaglecat.com interviewed 15 tech experts (I included).

  • Jenkins Pipeline

    The Jenkins Build Flow Plugin, started by Nicolas De Loof, was a huge success and, as a result,Koshuke decided to start…

  • The Need For Jenkins Pipeline

    Over the years, Jenkins has become the undisputed ruler among continuous integration (CI), delivery and deployment (CD)…

Others also viewed

Explore content categories