Interview with Victor Farcic – The DevOps 2.1 Toolkit Author

Interview with Victor Farnic - The DevOps 2.1 Toolkit AuthorHello, everyone! Welcome to Best Programming Books weekly special! Our featured author for today is Victor Farcic. We want to introduce him to all of you but the best introduction that we can give you is already written in his interview and it’s all complete and detailed.

Victor has written books that are now one of the best selling in Computers & Technology category, and it includes our featured book The DevOps 2.1 Toolkit: Docker Swarm: Building, testing, deploying, and monitoring services inside Docker Swarm clusters. He also wrote The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices, and together with Alex Garcia, they wrote Test-Driven Java Development.

We won’t make this long, so please enjoy reading and don’t forget to share this awesome interview with your friends!


Interview with Victor Farnic - The DevOps 2.1 Toolkit Author


Name: Viktor Farcic

Background: Viktor Farcic is a Senior Consultant at CloudBees, a member of the Docker Captains group, and books author.

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 favorite is Go.

His big passions are DevOps, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).

He often speaks at community gatherings and conferences (latest can be found here).

He published The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices, The DevOps 2.1 Toolkit: Docker Swarm: Building, testing, deploying, and monitoring services inside Docker Swarm clusters, and the Test-Driven Java Development.

His random thoughts and tutorials can be found in his blog

Favorite gadget: Google Home

Hobbies: Open source projects like Docker Flow


What is your book about, and why should our readers read it?

The DevOps 2.1 Toolkit: Docker Swarm: Building, testing, deploying, and monitoring services inside Docker Swarm clusters is an in depth exploration of Docker with focus on Docker Swarm. It goes beyond basic usage of the scheduler by exploring networking, service discovery, API, volumes, and secrets. It evaluates different ways to set up a cluster on-prem, on AWS, and DigitalOcean. Monitoring and centralized logging are first-class citizens.

The book provides hands-on experience.

What, in your opinion, is the current most exciting technological advancement and why?

Most of the current advancements are related to schedulers (Docker Swarm and Kubernetes). They work hand in hand with microservices and continuous deployment. I think that 2017 was dedicated mostly to those subjects.

In 2018 we’ll see the emergence of unikernels which might even replace containers. More widely adopted standards for serverless infrastructure will start to emerge allowing us to move away from vendor locking strategies. Machine learning and voice enabled automation will enter the mainstream.

What inspired you to write your book/s?

I believe in open source community and like sharing knowledge. Most of my time is spent on message boards, giving talks and workshops, and writing blogs. Books are an extension of those activities. They serve multiple purposes. First of all, writing books is my way of exploring interesting subjects in more depth. They force me to go into details I might not be inclined to go to otherwise.

My books are the result of a community effort. When I get an idea, I start exploring it and writing down the results. I do not have a scope defined in advance. Instead, I publish a book on as soon as only a few chapters are done. From there on, people start reading it and sending me their feedback. They tell me what they like and what should be changed. They notify me about the issues they’re encountering. Most importantly, readers are defining the direction. They tell me what they would like to read in the next chapter, what are the problems they’re facing and what are the issues they’d like to solve. Their feedback is what defines the scope of my books. My name is on the covers, but the books belong to the community around it.

If there’s one chapter in your book people should have read, which one should it be, and why?

That’s impossible to answer. Every book is a story with a beginning, middle, and the end. It would be like watching only a clip of a movie. It might get you energized to see the whole thing but, more often than not, it reveals parts of the story that should be seen entirely. Start from the beginning, continue if you like it.

As an author, which book made the most impact on you?

There are many. I like to read those written by Dan North and Gojko Adzic when I want something “light”. They are a good read in a bus or a plane. When I’m at home, I prefer more hands-on books. The Way To Go: A Thorough Introduction To The Go Programming Language was an excellent one. However, if I’d have to choose one that made the most impact on me, that would be Site Reliability Engineering: How Google Runs Production Systems. The ways they organized their infrastructure tasks is truly stunning and was a great inspiration for some of my works.

If there’s one subject you’d like to see a book about, what would it be?

I’d like to get my hands on a book about ChatOps. It is a subject that intrigues me lately and, as far as I know, no one wrote an in-depth exploration of the subject. I might my get my hands dirty and use that as inspiration for my next book if no one else beats me to it.

What would you like to ask the next author being interviewed?

Are the good things that come to people who wait, the leftovers of people who went before them?

Bonus Question from Thomas Mailund: Is Deckard a replicant?

Yes, he is.

Harrison Ford (claimed that he is no replicant) said to Ridley Scott: “OK, mate. You win! Anything! Just put it to rest.”


There we go! As always, we are very grateful to the authors that accepted our interview. TO Mr. Vitor Farcic, sir, thank you very, very much! We got his “yes” right away and answered our questions right away. Thank you so much sir! To our dear readers, thank you very much too for the never-ending support! See you all next week in our weekly special!

You may also like...