Distributed Services with Go, Travis Jeffery

I’ve recently read Distributed Services with Go as part of my morning reading ritual. I’ve been working on a new service with Go for our experimentation platform at Udemy. This service will be a Kubernetes sidecar. Our default technologies for services are Kotlin and SpringBoot at Udemy. But, Kotlin and SpringBoot aren’t good enough technologies to implement a Kubernetes sidecar solution that should be efficient in resource usage, bootstrap time, docker image size, etc. So, we decided to use Go. I’ve some limited Go experience from my side projects and open source contribution activities, but I haven’t written any production-ready Go service from scratch. I choose this book to fill my knowledge gap.

The book is a good journey while implementing a simple distributed storage service from scratch; it’s a logging service like Kafka. It saves produced records to the file system and lets you consume them as tracking your offsets.

The concepts and technologies that you’ll use while reading the book;

The above list is exciting to see how different technologies are in action to build a distributed service from scratch. But as you guess, most of the above technologies deserve a separate book. You won’t find much detail in the book; the book primarily focuses on the practical use-cases rather than how these technologies work.

I learned many good things;

I generally find it hard to read books that include much code, and it was the case also for this book. The codes are in the GitHub repo, but I would like to copy-paste them from the text to see step-by-step implementation in my IDE, but copying codes from the PDF is annoying. It would help if you had some pre-knowledge about the used technologies or learned them separately to entirely understand what’s happening with that technology. However, I like the practical approach of the book.

If you have already used these technologies in-depth, no need to learn their Go implementations, and have familiarity with distributed systems, then you can skip this book. Otherwise, I can recommend the book. Happy reading!


comments powered by Disqus