21 books like Learning OpenTelemetry

Kubernetes is the go-to tool for orchestrating a landscape of cooperating microservices, making it a crucial skill to master.

This book guided me through Kubernetes, from the basics, such as pods, services, and deployments, to more advanced topics, like its inner workings and auto-scaling resources. What I particularly appreciate is the balance between theory and practical examples, reinforced by exercises with GitHub-hosted source code, which I also found helpful as a starting point for building real-world applications.

A common reason for microservice projects to fail is a lack of understanding of how to build resilient and fault-tolerant microservices.

This book was a game-changer for me, providing essential strategies to address these challenges. It taught me how to avoid anti-patterns like Cascading Failures and embrace patterns like Circuit Breaker and Bulkhead to manage temporary network issues and overload situations. The real-world solutions it offers were immediately applicable to my projects.

Apache Kafka is the industry standard for real-time event streaming, an essential component for large-scale, high-performance microservice ecosystems.

Despite being new to Kafka when I read this book, it quickly brought me up to speed on key concepts that underpin its scalability and real-time capabilities, such as the commit log, topic partitions, and consumer groups. The book also introduces other critical Kafka features like the schema registry, Kafka Connect, and stream processing with Kafka Streams and ksqlDB. The practical examples provided were straightforward to apply and adapt to my own use cases.

No matter how advanced our tools for developing resilient and scalable microservices become, the million-dollar question remains: How do we effectively break up a monolith into microservices?

This book offers excellent guidance on this challenge. I found its starting point grounded in Domain-Driven Design and its concepts like Bounded Contexts and Aggregates particularly valuable. These concepts are key to mapping microservices to a real-world domain model. I also appreciate Sam’s advice, to begin with a few relatively large microservices aligned with Bounded Contexts and only break them into smaller services when there’s a clear business case for doing so.

There are quite a few books on web API design, but James’ book is my favorite. I like how the book delves into not only the technology of web APIs but also James’ unique approach to API design—known as the Align Define Design Refine method (ADDR).

This methodical approach to API design begins by aligning the team on the business capabilities to be exposed by the API. Subsequently, the team can model and design the API operations that implement those capabilities using the techniques described in the book.

It is a valuable methodology to have in any software team's design toolbox. I highly recommend James’s book.

You may know of Sugata’s work, even if the name does not ring a bell. He is the Indian professor who decided to cement an online computer into a wall in a slum in Delhi, set up a hidden camera, and waited to see how the local children would react. This was before everyone had a laptop or a mobile phone. The kids quickly gathered round and quickly figured out how to do all kinds of interesting things, without any teaching. Indeed, he found that when teachers tried to ‘help’, the children stopped being resourceful, stopped collaborating as independent learners, and expected to be taught. The School in the Cloud documents the growth of Sugata’s work and global influence since that first experiment, and reminds us forcibly of just how much all children can learn under their own steam – if we will just get out of the way. 

This anthology holds a special place in my heart. I received a copy of it as a Christmas present from my dear grandmother in 1979. Just holding it in my hands brings back so many happy memories of that long-departed lady. The book contains just eleven stories, but it is “a collection of deliciously scary fare.” Among the choice delicacies contained within its covers is the shortened version of A Christmas Carol made by Dickens for his public readings of the story, which I read in his imagined voice. Alongside anthology favourites by Hugh Walpole, Algenon Blackwood, and Jerome K. Jerome are less familiar, but equally rewarding ghostly tales by Marjorie Bowen, Oliver Onions, Margery Allingham, and others. I don’t know if it is still in print, but anyone who takes the trouble to find a copy will be richly rewarded. 

This is a book for practitioners, by a practitioner, full of practical learnings that I was able to start using in my work immediately.

I especially appreciated the parts teaching the core principles of infrastructure as code (e.g., systems are disposable, consistent, can easily be reproduced, etc.), core practices of infrastructure as code (e.g., use definition files, self-documented systems and processes, version all the things, etc.), and the idea of antifragile systems (rather than just systems that you prevent from breaking) and autonomic systems (rather than just automated systems).

In industry, your data is very likely to live within a data warehouse such as BigQuery, Redshift, or Snowflake. Therefore, to be an effective data scientist in the industry, you should learn how to use data warehouses effectively. 

Once you learn data warehousing and SQL with any one of these products, it is quite easy to pick up another. So which one do you start with?

You can use Snowflake on all three of the major public clouds. Because it’s a standalone product, it is the most similar to a “traditional” data warehouse and can be picked up easily even if you are not familiar with cloud computing. That makes it a good data warehouse to start with, and is the reason my second book pick is this book on Snowflake.

BigQuery is also available on all three major public clouds, but it works best (and is used most commonly)… show more.

While the term the “Metaverse” usually makes people think of a fully digital, immersive world, my own feeling is that technologies that bring digital information and entertainment into our physical world is a much more powerful and important arena. This leads us to the transformative and still-developing world of Augmented Reality.

David Rose of the MIT Media Lab has been working with Augmented Reality for more than a decade, and Supersight is an overview of what he's seen and what he’s learned in this time. 

What I love about Supersight is that while David is clearly as excited about this topic as I am, he’s also a realist, and openly discusses issues and challenges with Augmented Reality. Perhaps most valuable are the 14 Augmented Reality Design Principles that he outlines – super realistic, super useful.

After reading this, you’ll have a very grounded idea of the capabilities and potential of… show more.