59 books
—
58 voters
Goodreads helps you keep track of books you want to read.
Start by marking “Designing Data-Intensive Applications” as Want to Read:
Designing Data-Intensive Applications
by
ebook, Early Release - Raw & Unedited, 562 pages
Published
by O'Reilly
(first published April 25th 2015)
Friend Reviews
To see what your friends thought of this book,
please sign up.
Reader Q&A
To ask other readers questions about
Designing Data-Intensive Applications,
please sign up.
Be the first to ask a question about Designing Data-Intensive Applications
Community Reviews
Showing 1-30
Start your review of Designing Data-Intensive Applications
I consider this book a mini-encyclopedia of modern data engineering. Like a specialized encyclopedia, it covers a broad field in considerable detail. But it is not a practice or a cookbook for a particular Big Data, NoSQL or newSQL product. What the author does is to lay down the principles of current distributed big data systems, and he does a very fine job of it.
If you are after the obscure details of a particular product, or some tutorials and "how-to"s, go elsewhere. But if you want to unde ...more
If you are after the obscure details of a particular product, or some tutorials and "how-to"s, go elsewhere. But if you want to unde ...more
A must-read for every programmer. 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 where anyone can understand it.
I learned a lot about replication, partitioning, linearizability, locking, write skew, phantoms, transactions, event logs, and more. I'm ...more
I learned a lot about replication, partitioning, linearizability, locking, write skew, phantoms, transactions, event logs, and more. I'm ...more
Honestly, this one took me much more time than I've expected.
Plus, it's definitely one of the best technical books I've read in years - but still, it doesn't mean you should run straight away to your bookshop - read up to the end of the review first.
I'll risk the statement that this book's content will not be 100% directly applicable to your work, BUT it will make you a better engineer in general. It's like with reading books about Haskell - most likely you'll never use this language for any pra ...more
Plus, it's definitely one of the best technical books I've read in years - but still, it doesn't mean you should run straight away to your bookshop - read up to the end of the review first.
I'll risk the statement that this book's content will not be 100% directly applicable to your work, BUT it will make you a better engineer in general. It's like with reading books about Haskell - most likely you'll never use this language for any pra ...more
(5.0) excellent summary/foundation/recommendations for distributed systems development, covers a lot of the use cases for data-intensive (vs compute-intensive) apps/services. I recommend to anyone doing service development.
Recommendations are well-reasoned, citations are helpful and are leading me to do a lot more reading.
Thank you for finding and sharing this one, @Chet. I think this will be a book we assign as a primer for working at Goodreads going forward. At least some of the (later) chapte ...more
Recommendations are well-reasoned, citations are helpful and are leading me to do a lot more reading.
Thank you for finding and sharing this one, @Chet. I think this will be a book we assign as a primer for working at Goodreads going forward. At least some of the (later) chapte ...more
Some quite valuable content diluted with less useful content. I think I’d much prefer to read this author’s focused articles or blogs than recommend that someone slog through this.
I’m still not quite sure who the intended audience of this book is, but it’s definitely not me. The intro chapter discusses the example of Twitter’s fan-out writes and how they balanced typical users with celebrities who have millions of followers. Because of that intro, I expected a series of architecture patterns and ...more
I’m still not quite sure who the intended audience of this book is, but it’s definitely not me. The intro chapter discusses the example of Twitter’s fan-out writes and how they balanced typical users with celebrities who have millions of followers. Because of that intro, I expected a series of architecture patterns and ...more
Nov 22, 2017
David Bjelland
rated it
it was amazing
·
review of another edition
Shelves:
cs-software
Like you'd expect of a technical book with such a broad scope, there are sections that most readers in the target audience will probably find either too foundational or too esoteric to justify writing about at this kind of length, but still - at its best, I shudder to think of the time wasted groping in the dark for an ad hoc understanding of concepts it explains holistically in just a few unfussy, lucid pages and a diagram or two.
Definitely a book I see myself reaching for as a reference or me ...more
Definitely a book I see myself reaching for as a reference or me ...more
The perception of this depends on how much do you know already.
If you know a lot about serialization: JSON, Avro, Google Protocol Buffers, MessagePack, you name it; db data structures: WAL, B+Tree, LSM, you name it; distributed systems: consensus (Paxos, Raft), messaging (at-least-once, at-most, idempotence), partitioning, you won't gain a lot.
If you read tens of whitepapers, read _internals_ books, you won't gain a lot.
If you run Jepsen tests on your own product, you won't gain a lot.
But if yo ...more
If you know a lot about serialization: JSON, Avro, Google Protocol Buffers, MessagePack, you name it; db data structures: WAL, B+Tree, LSM, you name it; distributed systems: consensus (Paxos, Raft), messaging (at-least-once, at-most, idempotence), partitioning, you won't gain a lot.
If you read tens of whitepapers, read _internals_ books, you won't gain a lot.
If you run Jepsen tests on your own product, you won't gain a lot.
But if yo ...more
I recently used Spark to count all the data stores mentioned throughout the book.
There's a total of 72 products, where Apache ZooKeeper, PostgreSQL and MySQL are the ones most mentioned, with 46, 44 and 42 citations.
The complete list is available at https://medium.com/@irio/all-data-sto... ...more
There's a total of 72 products, where Apache ZooKeeper, PostgreSQL and MySQL are the ones most mentioned, with 46, 44 and 42 citations.
The complete list is available at https://medium.com/@irio/all-data-sto... ...more
At the beginning of reading this, I vacillated between a three-star and a four-star rating. The book is organised into three parts. The first part is about data storage on a single machine. Whenever it would cover material I already knew, I'd be mildly bored. Whenever it covered material that was unfamiliar to me, I found the explanations lucid and fascinating. I venture that I would have been as pleased with the topics I already knew about, had I not already known about them.
In part II, the boo ...more
In part II, the boo ...more
My full notes: https://juanignaciosl.github.io/learn...
IMHO this book is a modern classic, a must read for every software engineer and developer. I’m certain that it will be reread it from time. ...more
IMHO this book is a modern classic, a must read for every software engineer and developer. I’m certain that it will be reread it from time. ...more
Sep 22, 2017
Sameer Rahmani
rated it
it was amazing
·
review of another edition
Shelves:
distributed-software
It's a really great book. The author is well known in the field and the author of Apache Samza. In this book he explains even smallest challenges in creating a distributed data intensive system.
Just did a nuanced review on my tech blog, here: https://veekaybee.github.io/2019/04/1...
...more
This book changed my view to designing application!
What is the meaning of Data-Intensive?
We call an application data-intensive if data is its primary challenge- the quality of data, the complexity of data, or the speed at which it is changing.
Who should read this book?
I think that all developers must read this book. If you develop applications that have some kind of server/ backend for storing or processing data, and your application use the internet, then this book is for you.
Why should you, as ...more
What is the meaning of Data-Intensive?
We call an application data-intensive if data is its primary challenge- the quality of data, the complexity of data, or the speed at which it is changing.
Who should read this book?
I think that all developers must read this book. If you develop applications that have some kind of server/ backend for storing or processing data, and your application use the internet, then this book is for you.
Why should you, as ...more
Was it easy to read: It may have been the hardest thing I’ve ever read. The writing style is actually nice and quite colloquial for a technical book. But there is so much information in it! It took me ages (half a year) to get through it by taking notes when reading.
What I liked about it: The amount of information and the wast contexts that it covers: important concepts likes response time percentiles, linearisability, serializability and etc. explained; deep dive into database theory, different ...more
What I liked about it: The amount of information and the wast contexts that it covers: important concepts likes response time percentiles, linearisability, serializability and etc. explained; deep dive into database theory, different ...more
This book is monumental. It explains many aspects of designing data applications in a very approachable way. It has everything; from high level differences between SQL and NoSQL to low level details of how databases work. The explanations are clear and accompanied by code samples, diagrams and examples of data engines that work that way.
Part I of the book covers the fundamentals (e.g. how to handle data on a single machine). Part II covers Distributed data: how to handle it and issues you'll fa ...more
Part I of the book covers the fundamentals (e.g. how to handle data on a single machine). Part II covers Distributed data: how to handle it and issues you'll fa ...more
In this category, this is, perhaps, one of the best books that exist on the subject; however there’s nothing on this book about how to specifically design my own data-intensive applications. This is more an overview of different distributed database design ideas and the challenges of designing proper distributed database systems and applications. As an overview of those topics, this book is awesome, but it failed to delivered what the title proposes. I really felt enriched by broadening my under
...more
Often, We learn our skills by acquaintance and usually miss to cultivate the underlying knowledge of particular subject. Therefore we compensate it by another type of learning; by experience. But it's not always accurate and mostly based on hindsight which is why we need another layer knowledge to justify ours. These foundation of knowledge help us to giving better landscape to see the problem correspondingly. Hence, it could eventually make better decision (or trade off) for creators.
"Designin ...more
"Designin ...more
Probably the best written technical book I ever read. Martin Kleppman is vastly knowledgeable about all types and classes of databases and principles of data processing, but also uncannily talented in teaching others with clarity and a pinch of subtle humour. He covers the entire map of the territory that are data processing principles and systems with great detail (and delightfully toys with the map metaphor at the beginning of each new chapter), yet never gets bogged down. The book finishes of
...more
Sep 23, 2020
Miloš Milivojević
rated it
it was amazing
·
review of another edition
Shelves:
my-own-my-precious,
professional
Sometimes I think it's funny how hard it is for me to properly review a great book - even a technical one, where one would think reviewing comes easier. So, let's whip out the big guns right off the bat - this is probably the best technical book that I've ever read and it's very likely I'll be returning to it for a refresher from time to time.
But what makes it so great, an inquisitive mind might ask? There wasn't a lot of practical value in it, at least not of the kind that would be instantly ap ...more
But what makes it so great, an inquisitive mind might ask? There wasn't a lot of practical value in it, at least not of the kind that would be instantly ap ...more
The book gives comprehensive overview of design aspects for systems working with data. For each of them it goes deep enough to describe needed concepts and principles and implementation options. And if you want to go deeper, after each chapter there are big lists of references to relevant research papers, specific implementations etc. The book ends with a chapter where the author gives his subjective view on where the industry is moving. Which is distinct to the rest of the book but still is an
...more
A clear and detailed overview of the challenges modern applications have to face while dealing with data and the current state-of-the-art. From SSTables to event sourcing, Martin Kleppman gives great insights on what every engineer/architect should know when designing systems that deal with any kind of data. Highly recommended.
I wish I had this book 5 years go. A complete text on distributed systems that are extremely valuable for hands on experience. You have to read this book multiple times to get a good grasp on concepts on distributed computing. I do feel the title is little misleading for a solid texts on distributed systems. Highly recommended.
This is one of the best books for getting familiar with the fundamentals of big data technologies and why these tools are made like this. Most of the other books explain a particular set of technologies like Hadoop or Spark or ... but Martin Kleppman starts with the concepts and introduce these technologies as an example for the implementation.
The book is full of citations for people who want to learn more about each topic. The organization of topics into three different parts makes the book ea ...more
The book is full of citations for people who want to learn more about each topic. The organization of topics into three different parts makes the book ea ...more
Great book. Every software developer should definitely read it. It covers many topics, hard to remember everything, but it gives you a notion of systems/databases/tools/techniques used nowadays. You should be aware of trade-offs in every solution, before you use it and this book is a good start point.
Encyclopedic and fun. Not only is this book packed with info about modern database systems, and related systems, it's very engaging and provides enough references to keep you busy for a long time. My bookmarks list is surely going to take a long time to work through. The book is a geek treasure if you are not intimately familiar with the various topics covered.
| topics | posts | views | last activity | |
|---|---|---|---|---|
| Data Engineering: 2020 March/April: Designing Data-Intensive Applications | 1 | 12 | Apr 03, 2020 06:22AM | |
| Seven things to consider- create an app like Uber | 1 | 4 | Jan 23, 2020 11:13AM | |
| Futurice: Recommendation: Designing Data-Intensive Applications | 1 | 52 | Jul 06, 2017 04:41AM |
Goodreads is hiring!
Related Articles
If you haven't heard of record-smashing singer and songwriter Mariah Carey, is there any hope for you? Who else has sold more than 200 million...
57 likes · 23 comments
No trivia or quizzes yet. Add some now »
“In distributed systems, suspicion, pessimism, and paranoia pay off.”
—
6 likes
“The moral of the story is that a NoSQL system may find itself accidentally reinventing SQL, albeit in disguise.”
—
6 likes
More quotes…


















