![]() ![]() There is a good example of how a LinkedIn profile can be represented as a JSON document – the tree-like structure of a profile is a good fit to represent with JSON. This chapter discusses the well-known relational model and the document model (NoSQL). ![]() There is also a good point made about response times: when end-users require multiple back-end calls, many users may experience delays, even if only a fraction of individual requests are slow (tail latency amplification). I particularly liked the example of the evolution of how Twitter delivers tweets to followers. Foundations of Data SystemsĪn introductory chapter that defines reliability, scalability and maintainability. I really like the mix of references – some are to computer science papers from the 1970s and onwards, and many are to various blog posts. Each chapter ends with lots of references (between 30 and 110). There are three parts in the book: Foundations of Data Systems (chapters 1 – 4), Distributed Data (chapters 5 – 9), and Derived Data (chapters 10 – 12). ![]() There is so much to learn for me in this book, so I have summarized the main points from each chapter, with a special emphasis on what I found most interesting. I particularly like that the author Martin Kleppmann knows the theory very well, but also seems to have a lot of practical experience of the types of systems he describes. What a great book Designing Data-Intensive Applications is! It covers databases and distributed systems in clear language, great detail and without any fluff. ![]()
0 Comments
Leave a Reply. |