Back to Blog
Designingdata intensiveapplications5/8/2023 ![]() ![]() The first chapter “Reliable, Scalable, and Maintainable Applications” covers engineering goals for building applications, such as performance metrics, operations desiderata etc. I’d characterize the first part as dealing with the interface between data systems and regular users. ![]() There’s three parts to the book, all roughly equal in length, but not in the difficulty of the material. ![]() An badly written transaction will be quickly discovered at 1000 QPS, but less so at 10 QPS. And perhaps it’s even more important in this context in order to avoid hard to detect bugs. Even people who work with small data need to know these things. ![]() That is, applications dealing with TBs of data per day and processing of PBs of data. I’d argue though that the book deals with or can only provide advice for “data-intensive” applications. And that’s rather fitting because in such systems organizing and properly accessing data is the hard part. The core issue is, of course, handling data in single-machine and distributed systems - and handling lots of it. Thus it deals with databases, services, message queues and the like. Specifically, folks who need to deal with the backend of things. The target audience is builders of Internet applications. It’s the kind of book where you can genuinely feel a better developer at the end of it than at the start. The tl dr is that this is a very good book and you should go out and read it. This is a book review for Designing Data-Intensive Applications, by Martin Kleppmann. Designing Data Intensive Applications Review ![]()
0 Comments
Read More
Leave a Reply. |