The DevOps Toolkit Series (volumes 2 and 3)
The DevOps Toolkit Series (volumes 2 and 3)
$60.00
Regular Price
$50.00
Bundle Price

The DevOps Toolkit Series (volumes 2 and 3)

The DevOps 2.1 Toolkit: Docker Swarm
The DevOps 2.2 Toolkit: Self-Healing Clusters
The following 2 books are included in this bundle...

About the Bundle

  • Share this bundle

About the Books

The DevOps 2.1 Toolkit: Docker Swarm

The DevOps 2.1 Toolkit: Docker Swarm

Building, testing, deploying, and monitoring services inside Docker Swarm clusters
  • 1,035

    Readers

  • 400

    Pages

  • 100,682

    Words

  • 100%

    Complete

  • PDF

  • EPUB

  • MOBI

  • APP

The book envelops all aspects of building, testing, deploying, and monitoring services inside Docker Swarm clusters. We'll go through all the tools required for running a cluster. We'll go through the whole process with clusters running locally on a laptop. Once we are confident with the outcome, we'll translate the experience to different hosting providers like AWS, Azure, DigitalOcean, and so on.

The book goes deeper into one of the subjects explored in The DevOps 2.0 Toolkit. It is updated to use the latest and greatest features and techniques introduced in Docker 1.12.

We'll go through many practices and even more tools. While there will be a lot of theory, this is a hands-on book. You won't be able to complete it by reading it in a metro on a way to work. You'll have to read this book while in front of the computer and get your hands dirty.

The DevOps 2.2 Toolkit: Self-Healing Clusters

The DevOps 2.2 Toolkit: Self-Healing Clusters

Building Self-Adaptive And Self-Healing Docker Clusters
  • 194

    Readers

  • 80%

    Complete

  • PDF

  • EPUB

  • MOBI

  • APP

It seems that with each new book the scope gets fuzzier and less precise. When I started writing Test-Driven Java Development the scope of the whole book was done in advance. I had a team working with me. We defined the index and a short description of each chapter. From there on we worked on a schedule as most technical authors do. Then I started writing the second book. The scope was more obscure. I wanted to write about DevOps practices and processes and had only a very broad idea what will be the outcome. I knew that Docker had to be there. I knew that configuration management is a must. Microservices, centralized logging, and a few other practices and tools that I used in my projects were part of the initial scope. For that book, I had no one behind me. There was no team but me, a lot of pizzas, an unknown number of cans of Red Bull, and many sleepless nights. The result is The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices. With the third book, the initial scope became even more obscure. I started writing without a plan. It was supposed to be about cluster management. After a couple of months of work, I attended DockerCon in Seattle where we were presented with the new Docker Swarm Mode. My immediate reaction was to throw everything I wrote to trash and start over. I did not know what will the book be about except that it must be something about Docker Swarm. I was impressed with the new design. Something about Swarm ended up being The DevOps 2.1 Toolkit: Docker Swarm: Building, testing, deploying, and monitoring services inside Docker Swarm clusters. While working on it, I decided to make DevOps Toolkit Series. I thought that it would be great to record my experiences from different experiments, and from working with various companies and open source projects. So, naturally, I started thinking and planning the third installment in the series; The DevOps Toolkit 2.2. The only problem is that, this time, I truly don't have a clue what will it about. One idea was to do a deep comparison of different schedulers (e.g. Docker Swarm, Kubernetes, and Mesos/Maraton). The another was to explore serverless. Even though it is a terrible name (there are servers, we just don't manage them), it is a great subject. The ideas kept coming but there was no clear winner. So, I decided not to define the scope. Instead, I defined some general objectives.

The goals I set in front of me is to build a self-adaptive and self-healing system based on Docker. The only problem is that I do not yet know how I will do that. There are different bits of practices and tools I've been using, but there is no clearly visible light at the end of the tunnel. Instead of defining what the book will be, I defined what I want to accomplish. You can think of this book as my recording of the journey. I will need to explore a lot. I will probably need to adopt some new tools and write some code myself. I don't know, yet. Maybe it will turn out to be something completely different, and there will not be a self-adaptive and self-healing system. We'll see. Think of this book as "Viktor's diary while trying to do stuff."

So, for now, the objectives are to go beyond a simple setup of a cluster, services, continuous deployment, and all the other things you probably already know. If you don't, read my older books. I do not yet know the scope, nor I know what will be the result. Typically, when you write a book, you start with an outline and an index, write your chapters one by one and, at the end of the process, write a preface. It makes us (authors) look intelligent and in control. That is not the case. I did not write the preface at the end of the process (as an editor would advise me). I'm trying to be honest with you. I don't have a plan.

You've been warned! I don't know where this book is going nor whether I will manage to fulfill my self-defined objectives. I'll do my best to outline the steps towards a self-adapting and self-healing system in the same way as I am exploring them myself.

About the Author

Viktor Farcic
Viktor Farcic

Viktor Farcic is a Senior Consultant at CloudBees and a member of the Docker Captains group.

He coded using a plethora of languages starting with Pascal (yes, he is old), Basic (before it got Visual prefix), ASP (before it got .Net suffix), C, C++, Perl, Python, ASP.Net, Visual Basic, C#, JavaScript, Java, Scala, etc. He never worked with Fortran. His current favourite is Go.

His big passions are Microservices, Continuous Deployment and Test-Driven Development (TDD).

He often speaks at community gatherings and conferences.

The Leanpub Unconditional, No Risk, 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms

Write and Publish on Leanpub

Authors and publishers use Leanpub to publish amazing in-progress and completed ebooks, just like this one. You can use Leanpub to write, publish and sell your book as well! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub