Here are 32 books that Kafka in Action fans have personally recommended if you like
Kafka in Action.
Shepherd is a community of 11,000+ authors and super readers sharing their favorite books with the world.
Shepherd is reader supported. When you buy books, we may earn an affiliate commission.
My passion for developing production-ready, cooperating microservices began in 2008 when I first started assisting customers in creating distributed systems—long before the term “microservices” was coined. During that time, I faced significant challenges, including grappling with the “Eight Fallacies of Distributed Computing”. Since then, I’ve dedicated most of my career to deepening my understanding of these complexities and finding ways to address them through robust architecture, design patterns, and the right tools.
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.
With Kubernetes, users don't have to worry about which specific machine in their data center their application is running on. Each layer in their application is decoupled from other layers so they can scale, update, and maintain them independently.
Kubernetes in Action teaches developers how to use Kubernetes to deploy self-healing scalable distributed applications. By the end, readers will be able to build and deploy applications in a proper way to take full advantage of the Kubernetes platform.
My passion for developing production-ready, cooperating microservices began in 2008 when I first started assisting customers in creating distributed systems—long before the term “microservices” was coined. During that time, I faced significant challenges, including grappling with the “Eight Fallacies of Distributed Computing”. Since then, I’ve dedicated most of my career to deepening my understanding of these complexities and finding ways to address them through robust architecture, design patterns, and the right tools.
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.
A single dramatic software failure can cost a company millions of dollars - but can be avoided with simple changes to design and architecture. This new edition of the best-selling industry standard shows you how to create systems that run longer, with fewer failures, and recover better when bad things happen. New coverage includes DevOps, microservices, and cloud-native architecture. Stability antipatterns have grown to include systemic problems in large-scale systems. This is a must-have pragmatic guide to engineering for production systems. If you're a software developer, and you don't want to get alerts every night for the rest of your…
My passion for developing production-ready, cooperating microservices began in 2008 when I first started assisting customers in creating distributed systems—long before the term “microservices” was coined. During that time, I faced significant challenges, including grappling with the “Eight Fallacies of Distributed Computing”. Since then, I’ve dedicated most of my career to deepening my understanding of these complexities and finding ways to address them through robust architecture, design patterns, and the right tools.
Understanding how requests and messages traverse a large microservice landscape is notoriously challenging. The CNCF OpenTelemetry framework standardizes how to collect and observe telemetry data (metrics, logs, and traces).
This book was invaluable in helping me grasp OpenTelemetry’s core concepts and architecture, including collectors and exporters, and how to instrument applications effectively. It also helped me understand how distributed tracing data is structured into traces and spans and how to propagate context information between cooperating microservices.
OpenTelemetry is a revolution in observability data. Instead of running multiple uncoordinated pipelines, OpenTelemetry provides users with a single integrated stream of data, providing multiple sources of high-quality telemetry data: tracing, metrics, logs, RUM, eBPF, and more. This practical guide shows you how to set up, operate, and troubleshoot the OpenTelemetry observability system.
Authors Austin Parker, head of developer relations at Lightstep and OpenTelemetry Community Maintainer, and Ted Young, cofounder of the OpenTelemetry project, cover every OpenTelemetry component, as well as observability best practices for many popular cloud, platform, and data services such as Kubernetes and AWS Lambda. You'll learn…
My passion for developing production-ready, cooperating microservices began in 2008 when I first started assisting customers in creating distributed systems—long before the term “microservices” was coined. During that time, I faced significant challenges, including grappling with the “Eight Fallacies of Distributed Computing”. Since then, I’ve dedicated most of my career to deepening my understanding of these complexities and finding ways to address them through robust architecture, design patterns, and the right tools.
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.
How do you detangle a monolithic system and migrate it to a microservice architecture? How do you do it while maintaining business-as-usual? As a companion to Sam Newman's extremely popular Building Microservices, this new book details a proven method for transitioning an existing monolithic system to a microservice architecture.
With many illustrative examples, insightful migration patterns, and a bevy of practical advice to transition your monolith enterprise into a microservice operation, this practical guide covers multiple scenarios and strategies for a successful migration, from initial planning all the way through application and database decomposition. You'll learn several tried and tested…
I am motivated by working on products that many people use. I've been a part of companies that deliver products impacting millions of people. To achieve it, I am working in the Big Data ecosystem and striving to simplify it by contributing to Dremio's Data LakeHouse solution. I worked on projects using Spark, HDFS, Cassandra, and Kafka technologies. I have been working in the software engineering industry for ten years now, and I've tried to share my experience and lessons learned in the Software Mistakes and Tradeoffs book, hoping that it will allow current and the next generation of engineers to create better software, leading to more happy users.
The Database Internals will allow you to go one step further in your understanding of how distributed databases work.
The author has a lot of experience with one of the most successful distributed databases - Apache Cassandra and shares his knowledge about low-level details and internals of distributed databases.
When it comes to choosing, using, and maintaining a database, understanding its internals is essential. But with so many distributed databases and tools available today, it's often difficult to understand what each one offers and how they differ. With this practical guide, Alex Petrov guides developers through the concepts behind modern database and storage engine internals.
Throughout the book, you'll explore relevant material gleaned from numerous books, papers, blog posts, and the source code of several open source databases. These resources are listed at the end of parts one and two. You'll discover that the most significant distinctions among many…
I’ve spent more than a decade working on infrastructure, from my early days at LinkedIn, where we had to do a massive DevOps transformation to save the company, to co-founding Gruntwork, where I had the opportunity to work with hundreds of companies on their software delivery practices. From all of this, I can say the following with certainty: the DevOps best practices that a handful of the top tech companies have figured out are not filtering down to the rest of the industry. This is making the entire software industry slower, less effective, and less secure—and I see it as my mission to fix that.
This is the best overview of data storage and distributed systems—two key concepts for building almost any piece of software today—that I've seen anywhere. Martin does a wonderful job of taking a massive body of research and distilling complicated concepts and difficult trade-offs down to a level anyone can understand.
I learned a lot about replication, partitioning, linearizability, locking, write skew, phantoms, transactions, event logs, and more. I'm also a big fan of the final chapter, The Future of Data Systems, which covers ideas such as "unbundling the database", end-to-end event streams, and an important discussion on ethics in programming and data systems.
Data is at the center of many challenges in system design today. Difficult issues need to be figured out, such as scalability, consistency, reliability, efficiency, and maintainability. In addition, we have an overwhelming variety of tools, including NoSQL datastores, stream or batch processors, and message brokers. What are the right choices for your application? How do you make sense of all these buzzwords? In this practical and comprehensive guide, author Martin Kleppmann helps you navigate this diverse landscape by examining the pros and cons of various technologies for processing and storing data. Software keeps changing, but the fundamental principles remain…
I’ve been running the MrExcel website since 1998 and have written 66 books about Excel. I am an Excel generalist – I know a fair amount about almost every aspect of Excel. But I respect the specialists who become experts on one part of Excel and offer deep knowledge dives into those portions of Excel. Cleaning data with Power Query, calculating “impossible” calculations with DAX, and then presenting them on interactive dashboards are some of the deep dives that you will learn on this list.
Microsoft quietly slipped the Get & Transform tools onto the Data tab in Excel in 2016. These tools are incredibly powerful – you clean your data once and Excel will remember how to clean your data every month, every week, every day, every hour. Ken Puls and Miguel Escobar will show you all of the best tricks for using these tools.
Power Query is the amazing new data cleansing tool in both Excel and Power BI Desktop. Do you find yourself performing the same data cleansing steps day after day? Power Query will make it faster to clean your data the first time. While Power Query is powerful, the interface is subtle—there are tools hiding in plain sight that are easy to miss. Go beyond the obvious and take Power Query to new levels with this book.
Like most geeks, I've always loved efficiency and productivity. Coming from a Windows-dominated world, the command line I was faced with in my CompSci degree was Initially mystifying, but over time I have come to see it as the most powerful human-computer interface out there. After spending years wresting with the command line at work, I decided to write a book on bash, and have blogged extensively on this and related topics. I also run live courses on bash and the command line for O'Reilly. There's nothing I enjoy more than opening people's eyes to the power of the shell!
Regular expressions are the cornerstone of command line wizardry.
They are used in pretty much all command-line tools, and all programming languages.
If you read this book, you'll have a deep understanding of what's going on, and the knowledge to go from hand-waving and guessing your way through regular expression writing to the mastery the book promises.
Regular expressions are an extremely powerful tool for manipulating text and data. They are now standard features in a wide range of languages and popular tools, including Perl, Python, Ruby, Java, VB.NET and C# (and any language using the .NET Framework), PHP, and MySQL. If you don't use regular expressions yet, you will discover in this book a whole new world of mastery over your data. If you already use them, you'll appreciate this book's unprecedented detail and breadth of coverage. If you think you know all you need to know about regular expressions, this book is a stunning eye-opener.…
Jeremy N. Smith is the author of three acclaimed narrative non-fiction books, including Breaking and Entering, about a female hacker called “Alien” and the birth of our information insecurity age. He has written for The Atlantic, Discover, Slate, and the New York Times, among other outlets, and he and his work have been featured by CNN, NPR, NBC Nightly News, The Today Show, and Wired. He hosts The Hacker Next Door podcast and lives in Missoula, Montana.
The New Hacker’s Dictionary is the foremost compilation of the first fifty years of hacker lore, combining hilarious anecdotes and definitions to illuminate a hugely-influential but wildly-misunderstood culture more similar to beer-brewing monks than black-clad criminals. Though last updated in 1996, the technology, terms, and theories explained within still underlie the modern Internet, making this dictionary a dual cultural and architectural blueprint for anyone interested in how computing got to the present moment—and how to build a better future.
This new edition of the hacker's own phenomenally successful lexicon includes more than 100 new entries and updates or revises 200 more.
This new edition of the hacker's own phenomenally successful lexicon includes more than 100 new entries and updates or revises 200 more. Historically and etymologically richer than its predecessor, it supplies additional background on existing entries and clarifies the murky origins of several important jargon terms (overturning a few long-standing folk etymologies) while still retaining its high giggle value.
Sample definition
hacker n. [originally, someone who makes furniture with an axe] 1. A person who enjoys exploring the…
My passion for computer science started while spending my free time gaming in my young adult days, leading me to experiment with C++ and then dive into enterprise-level Java applications during high school. My enthusiasm for Java propelled me to teach and share my knowledge through Java and Spring tutorials on YouTube. I also frequent conferences where I exchange ideas on various software topics. My constant wish to contribute further to the community is filled by writing technical books. This mix of teaching, creating, and constant learning fuels me and pushes me further into the tech world. I really hope you will enjoy this selection of technical books!
This is another amazing book that offers a fresh view of microservice architecture and its benefits and challenges.
Besides advice on designing and managing microservices for large-scale Java applications, the part that stuck out to me the most was the deep dive into cloud-native development and the "Just enough Application Server (JeAS)" approach.
Any book that makes me rethink and improve my strategies for building resilient and robust apps is a gem.
Microservices break down a large application into smaller components, each interacting with each other to create a united whole. As each component can start, stop, and scale independently, so the whole system benefits from better fault-tolerance and resilience.
Enterprise Java Microservices is an example-rich tutorial that shows readers how to design and manage large-scale Java applications as a collection of microservices.
Key features
* The microservices mental model
* Fault tolerance with Netflix Hystrix
* Securing your microservices
* Deploying to the cloud
Audience
This book is for Java developers familiar with distributed n-tier application architecture.
