Designing Data-intensive Application: Why is the book written in the way it was

Structure and logics between chapters of a book is like the skeleton of human. Being aware of and familiar with this helps reading in many ways. For example, it helps remembering/reasoning out the knowledge of leafs of a knowledge tree (why the brain likely dizzies is because it sits at the top of your skeleton)

However, the book does not have such a skeleton diagram with itself. This post is posted with the target in mind to fill this blank.

The skeleton diagram will be updated as the poster reads through the book. Comments and advice any time from anyone will be welcomed.

（This figure serves as a general example of a skeleton. It by no means indicate the skeleton of the book concerned.)






补充内容 (2020-4-29 02:58):
如果有那么一瞬间这个帖子给了你一点好感：不加米吗亲?😎  重度搜索使用者表示缺米🥺 (Yes I plagiarized myself)

Skeleton for Ch 5 & 6

Due to the same hardware environment (multiple nodes) and similar data distribution pattern (split & copies), the knowledge in Ch 5 (Replication). & Ch 6 (Partition) highly overlap with each other. It was painful for me to read and understand them. Thus I try to construct the knowledge in a different and combined way, to see if changing the explaining way helps.

Two graphs were drawn for knowledge in Ch 5 & 6.

Graph 1: A demonstrating & concrete example of multiple nodes deployment which meet needs of both computers and data. Though, according to Martin, Multi-leaders mode (as Graph 1 adopts) is not often used in reality.

Based on Graph 1, Graph 2, which is the skeleton of knowledge, will be much easier to understand. Graph 2 is to be updated.

补充内容 (2020-5-6 13:05):
Graph 2 was updated and posted on 13rd 垅

补充内容 (2020-5-6 13:06):
Obviously, knowledge in these two chapters are so complicated linked with each other. Readers will had a hard time to generate an clear overal picture of the two without explicit drawing it.

I have finished brief-reading the book and accordingly update the skeleton. Every chapter is included now.
Replacing handwritten text by computer text seems to be wise choice, making the diagram neat and easier to maintain.

Currently the lines are crossing each other, which is a big problem against neatness

I have also been trying to structure the (the most essential?) skeleton of content for each chapter. I will post them in this post as well. The following is for Chapter 2.

I am drawing the skeleton as a method of reviewing. It involves a lot of thinking and helps you spot content that you didn't digest well.


\

Actually, anyone would like to help me to search on the web if someone has already done the work? Somehow I cannot access to any search engine.

This is what I've got for the current moment. Hopefully it can be enlarged by the browsers.

Chapter 1 seems better to be at the center of the skeleton, as everything else serves for the objectives proposed in it.


补充内容 (2020-4-29 18:17):
Martin seems to agree: (page 489 ) “...reliable,  scalable, and  maintainable. These themes have run through all of the chapters...”

Seems Martin put a knowledge tree alike graph at the end of every chapter. For example:

They are somewhat - I will not say largely - related to the skeleton & structures of the book


补充内容 (2020-5-3 12:08):
Correct: the graph for the chapter following it. So it’s actually at the the front of a chapter. It shows how the knowledge/tech in the following chapter linked to each other.

补充内容 (2020-5-3 12:09):
Correct: the graph 【is】 for the chapter ...

Skeleton for Ch 3

补充内容 (2020-5-6 10:30):
Correct: “Index tech for...” (left) should be “Techs for storage and index of...”

辛苦了。但看书重在有自己的理解

兔米搜索不是不扣分吗？楼主不会不知道吧