{"topic":{"id":11603,"title":"《System design interview》随缘记录帖","slug":"topic","userId":178,"categoryId":4,"createdAt":"2024-04-21 14:41:22.088801","bumpedAt":"2024-05-20 08:17:15.798309","views":430,"postsCount":17,"highestPostNumber":17,"likeCount":8,"closed":false,"pinned":false,"pinnedGlobally":false,"pinnedAt":null,"pinnedUntil":null,"isBanner":false,"excerpt":"最近在 x 上看到有朋友推了这本书，然后和另一位快手 + 腾讯爷聊的时候发现他对此书也十分推崇。因此计划在休息的时候随缘看看，有困惑/想法在此记录 https://github.com/Vonng/ddia","deletedAt":null,"isAnonymous":false,"isPrivate":false,"isMembersOnly":false,"category":{"id":4,"name":"谈笑风生","slug":"general","color":"25AAE2"},"author":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif"},"realAuthor":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif"},"tags":[]},"posts":[{"id":30358,"postNumber":1,"raw":"最近在 x 上看到有朋友推了这本书，然后和另一位快手 + 腾讯爷聊的时候发现他对此书也十分推崇。因此计划在休息的时候随缘看看，有困惑/想法在此记录\nhttps://github.com/Vonng/ddia","cooked":"

最近在 x 上看到有朋友推了这本书，然后和另一位快手 + 腾讯爷聊的时候发现他对此书也十分推崇。因此计划在休息的时候随缘看看，有困惑/想法在此记录

\n","createdAt":"2024-04-21 14:41:22.192621","updatedAt":"2024-05-20 12:50:01.094167","replyToPostNumber":null,"replyCount":0,"likeCount":2,"wordCount":70,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"❤️","count":2,"users":[{"id":30,"username":"一只玉米人","name":"玉米🌽"},{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old"}],"hasReacted":false}],"wiki":false,"version":2,"publicVersion":2,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":30361,"postNumber":2,"raw":"看起来是讲分布式数据库的设计理念的","cooked":"

看起来是讲分布式数据库的设计理念的

\n","createdAt":"2024-04-21 14:43:33.150255","updatedAt":"2024-05-06 06:25:41.578572","replyToPostNumber":null,"replyCount":0,"likeCount":0,"wordCount":17,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old","avatarUrl":"/uploads/image/43/32/4332638c11248b8ff07033c11de0759a55205facfbec85e14458245a91991faf.avif","admin":false,"moderator":false,"signatureRaw":null,"signatureCooked":null}},{"id":30388,"postNumber":3,"raw":"# Chapter 1: 可靠性、可伸缩性和可维护性\n互联网如此鬼斧神工，常常使人忘记这是人造产物。\n\nOS 课中我们学过，任务分为：计算密集型和 IO 密集型。如今很多应用程序都是 **数据密集型（data-intensive）** ，而非 **计算密集型（compute-intensive）**，因此我们必须对数据的处理进行优雅的设计。\n\n## 可靠性\n> **可靠性（Reliability）：** 在出现问题时，也能完成预期工作。\n\n- 造成错误的原因叫做 **故障（fault）** ，能预料并应对故障的系统特性可称为 **（一定范围内的）容错（limited-fault-tolerant）** 或 **回弹性（resilient）** 。\n- **故障（fault）** 不同于 **失效（failure）**， **故障** 通常定义为系统的一部分状态偏离其标准，而 **失效** 则是系统作为一个整体停止向用户提供服务。\n- 我们的目的是：即使发生 fault，但不至于 failure。可以通过“主动”fault 来测试系统的稳健性，进而进行提升。\n- 硬件故障、软件错误、人为错误。（更全面的硬件支持，更严格的软件工程……）\n\n## 可伸缩性\n> **可伸缩性（Scalability）：** 描述系统应对负载增长的能力。\n\n考虑 twitter 的两个业务：\n- 发布推文：用户可以向其粉丝发布新消息（平均 4.6k 请求 / 秒，峰值超过 12k 请求 / 秒）。\n- 主页时间线：用户可以查阅他们关注的人发布的推文（300k 请求 / 秒）。\n\n> 方法一该方法面对大量主页时间线会难以维系效率。\n![image|690x455](/uploads/image/b7/73/b773621b53d0693e4081d63b0f26544cc2df0ad9968cbb37b53e243dbd16a88b.avif)\n\n\n>方法二类似于读写的解耦，读的需求量远远高于写，并且需要在实际中和方法一相互结合，以避免头部博主一篇推文能产生百万、千万甚至更高次数的请求。。\n![image|690x334](/uploads/image/21/0c/210c20ab92cce06d14d3063555b1875cc9fd6c4f47462a1a125ae13181960c06.avif)\n\n### 延迟与响应时间\n- **响应时间（response time）** 是客户所看到的，除处理请求的时间（ **服务时间（service time）** ）外，还包括网络延迟和排队延迟的时间。\n- **延迟（latency）** 是某个请求等待处理的 **持续时长** ，在此期间它处于 **休眠（latent）** 状态，并等待服务。\n\n### 性能评价\n一般使用百分位点。例如响应时间中位数是 200 毫秒，这意味着一半请求的返回时间少于 200 毫秒，另一半比这个要长。\n**当一个请求需要多个后端请求时，单个后端慢请求就会拖慢整个终端用户的请求**\n\n## 可维护性\n> 我们总是听到“屎山代码”，但我连屎山也不会写。\n\n为了避免自己的软件系统变成遗留系统，我们特别关注软件系统的三个设计原则：\n* 可操作性（Operability）便于运维团队保持系统平稳运行。\n* 简单性（Simplicity）从系统中消除尽可能多的 **复杂度（complexity）**，使新工程师也能轻松理解系统（注意这和用户接口的简单性不一样）。\n* 可演化性（evolvability）使工程师在未来能轻松地对系统进行更改，当需求变化时为新应用场景做适配。也称为 **可扩展性（extensibility）**、**可修改性（modifiability）** 或 **可塑性（plasticity）**。\n\n简化系统并不一定意味着减少功能；也可以意味消除 **额外（accidental）** 的复杂度（因实现方式的落后导致的复杂）。消除 **额外复杂度** 的最好工具之一是 **抽象（abstraction）** 。","cooked":"

Chapter 1: 可靠性、可伸缩性和可维护性

互联网如此鬼斧神工，常常使人忘记这是人造产物。

OS 课中我们学过，任务分为：计算密集型和 IO 密集型。如今很多应用程序都是 数据密集型（data-intensive） ，而非 计算密集型（compute-intensive），因此我们必须对数据的处理进行优雅的设计。

可靠性

\n
可靠性（Reliability）： 在出现问题时，也能完成预期工作。
\n

造成错误的原因叫做 故障（fault） ，能预料并应对故障的系统特性可称为 （一定范围内的）容错（limited-fault-tolerant） 或 回弹性（resilient） 。
故障（fault） 不同于 失效（failure），故障通常定义为系统的一部分状态偏离其标准，而失效则是系统作为一个整体停止向用户提供服务。
我们的目的是：即使发生 fault，但不至于 failure。可以通过“主动”fault 来测试系统的稳健性，进而进行提升。
硬件故障、软件错误、人为错误。（更全面的硬件支持，更严格的软件工程……）

可伸缩性

\n
可伸缩性（Scalability）： 描述系统应对负载增长的能力。
\n

考虑 twitter 的两个业务：

发布推文：用户可以向其粉丝发布新消息（平均 4.6k 请求 / 秒，峰值超过 12k 请求 / 秒）。
主页时间线：用户可以查阅他们关注的人发布的推文（300k 请求 / 秒）。

\n
方法一该方法面对大量主页时间线会难以维系效率。
\n $\"image\"$
\n

\n
方法二类似于读写的解耦，读的需求量远远高于写，并且需要在实际中和方法一相互结合，以避免头部博主一篇推文能产生百万、千万甚至更高次数的请求。。
\n $\"image\"$
\n

延迟与响应时间

响应时间（response time） 是客户所看到的，除处理请求的时间（ 服务时间（service time） ）外，还包括网络延迟和排队延迟的时间。
延迟（latency） 是某个请求等待处理的 持续时长 ，在此期间它处于 休眠（latent） 状态，并等待服务。

性能评价

一般使用百分位点。例如响应时间中位数是 200 毫秒，这意味着一半请求的返回时间少于 200 毫秒，另一半比这个要长。
\n当一个请求需要多个后端请求时，单个后端慢请求就会拖慢整个终端用户的请求

可维护性

\n
我们总是听到“屎山代码”，但我连屎山也不会写。
\n

为了避免自己的软件系统变成遗留系统，我们特别关注软件系统的三个设计原则：

可操作性（Operability）便于运维团队保持系统平稳运行。
简单性（Simplicity）从系统中消除尽可能多的 复杂度（complexity），使新工程师也能轻松理解系统（注意这和用户接口的简单性不一样）。
可演化性（evolvability）使工程师在未来能轻松地对系统进行更改，当需求变化时为新应用场景做适配。也称为 可扩展性（extensibility）、可修改性（modifiability） 或 可塑性（plasticity）。

简化系统并不一定意味着减少功能；也可以意味消除 额外（accidental） 的复杂度（因实现方式的落后导致的复杂）。消除 额外复杂度 的最好工具之一是 抽象（abstraction） 。

\n","createdAt":"2024-04-21 15:46:29.153504","updatedAt":"2024-04-21 15:48:28.424534","replyToPostNumber":null,"replyCount":1,"likeCount":1,"wordCount":980,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"❤️","count":1,"users":[{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old"}],"hasReacted":false}],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":30389,"postNumber":4,"raw":"[quote=\"rotartsinimdA, post:3, topic:11603, username:Hypocrisy\"]\n## 可维护性\n\n> 我们总是听到“屎山代码”，但我连屎山也不会写。\n[/quote]\n\nhttps://xjtu.app/t/the-twelve-factor-app/11572","cooked":"

\n\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\trotartsinimdA:\n\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t

\n
可维护性
\n
\n
我们总是听到“屎山代码”，但我连屎山也不会写。
\n
\n

\n\t\t\t\t\t\t

\n $\"anonymous_coward_old\"$ \n anonymous_coward_old — #1 in The Twelve-Factor App\n

The Twelve-Factor App
\nIntroduction

In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps that:

Use declarative formats for setup automation, to minimize time and cost for new developers joining the project;\nHave a clean contract with the underlying operating system, offering maximum portability between execution environments;\nAre suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration;\nMinimize divergence between development and production, enabling continuous deployment for maximum agility;\nAnd can scale up without significant changes to tooling, architecture, or development practices.\n

The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc).
\nBackground

The contributors to this document have been directly involved in the development and deployment of hundreds of apps, and indirectly witnessed the development, operation, and scaling of hundreds of thousands of apps via our work on the Heroku platform.

This document synthesizes all of our experience and observations on a wide variety of software-as-a-service apps in the wild. It is a triangulation on ideal practices for app development, paying particular attention to the dynamics of the organic growth of an app over time, the dynamics of collaboration between developers working on the app’s codebase, and avoiding the cost of software erosion.

Our motivation is to raise awareness of some systemic problems we’ve seen in modern application development, to provide a shared vocabulary for discussing those problems, and to offer a set of broad conceptual solutions to those problems with accompanying terminology. The format is inspired by Martin Fowler’s books Patterns of Enterprise Application Architecture and Refactoring.
\nWho should read this document?

Any developer building applications which run as a service. Ops engineers who deploy or manage such applications.
\nThe Twelve Factors
\nI. Codebase
\nOne codebase tracked in revision control, many deploys
\nII. Dependencies
\nExplicitly declare and isolate dependencies
\nIII. Config
\nStore config in the environment
\nIV. Backing services
\nTreat backing services as attached resources
\nV. Build, release, run
\nStrictly separate build and run stages
\nVI. Processes
\nExecute the app as one or more stateless processes
\nVII. Port binding
\nExport services via port binding
\nVIII. Concurrency
\nScale out via the process model
\nIX. Disposability
\nMaximize robustness with fast startup and graceful shutdown
\nX. Dev/prod parity
\nKeep development, staging, and production as similar as possible
\nXI. Logs
\nTreat logs as event streams
\nXII. Admin processes
\nRun admin/management tasks as one-off processes

","createdAt":"2024-04-21 15:50:42.037834","updatedAt":"2024-05-06 06:25:41.661153","replyToPostNumber":3,"replyCount":0,"likeCount":0,"wordCount":34,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old","avatarUrl":"/uploads/image/43/32/4332638c11248b8ff07033c11de0759a55205facfbec85e14458245a91991faf.avif","admin":false,"moderator":false,"signatureRaw":null,"signatureCooked":null}},{"id":30431,"postNumber":5,"raw":"# Chapter2: 数据模型与查询语言\n\n*人的想象永远无法挣脱认知的局限*\n\n数据模型影响软件的构建方式，也影响问题解决的思考方式。\n\n## 关系模型与文档模型\n\n> 关系模型：数据被组织成关系（Table），每个关系是元组（Tuple，Row）的**无序**集合。\n\n## 对象关系不匹配\n\n面向对象（OOP）的编程语言被广泛用于应用开发，但是这与 SQL 数据模型之间存在转换的困难，需要引入额外的转换层。\n\n例如，我们可以使用多个表来存储一份简历中会涉及到的内容，如 Position、Education 等，但是实际上对于这样的文档，使用 json 来存储十分方便，它相对于多表模式存在更好的局部性（locality）。\n\n## 多对一和多对多的关系\n\n有些属性我们并不会选择使用纯文本字符来存储，而是以 ID 来记录。二者的权衡是一个副本（Duplication）问题，ID 信息对人类无意义，但在数据库中有关系映射；文本信息则在每处都对人类有意义。\n\n但是 ID 好处在于永远不需要改变，我们只需要更新其所映射的内容，即可自动更新所有信息，而文本信息则需要对所有的副本进行更改，这难免会产生遗漏，进而产生不一致风险。（去除这样的重复是数据库规范化思想之一，是三大范式的第？范式（忘记了））\n\n在表示多对一和多对多的关系时，关系数据库和文档数据库并没有根本的不同：在这两种情况下，相关项目都被一个唯一的标识符引用，这个标识符在关系模型中被称为**外键**，在文档模型中称为**文档引用**\n\n对高度关联的数据而言，文档模型是极其糟糕的，关系模型是可以接受的，而选用图形模型（后文会讲）是最自然的。\n\n## 文档模型中的模式灵活性\n\n文档数据库有时称为**无模式（schemaless）**，但这具有误导性，因为读取数据的代码通常假定某种结构 —— 即存在隐式模式，但**不由数据库强制执行**。更精确的术语是**读时模式**（schema-on-read，数据的结构只在数据被读取时才被解释），相应的是**写时模式**（schema-on-write，传统的关系数据库方法中，模式明确，且数据库确保所有的数据都符合其模式）。读时模式类似于编程语言中的动态（运行时）类型检查，而写时模式类似于静态（编译时）类型检查。\n\n![image|690x356](/uploads/image/5f/4e/5f4e6f5fc3ab9a87d80b3847c5c5a9e7b8686a4eb4c4266c8d8ae46b5b811d28.avif)\n\nMySQL 在执行 ```ALTER TABLE ``` 时会复制整个表，这可能意味着在更改一个大型表时会花费几分钟甚至几个小时的停机时间。大型表运行 ``` UPDATE ``` 是一个巨大的开销，我们可以使用读取时填充的策略，类似于第一章中，仅在需要时拉取信息。\n\n## 数据查询语言\n\nSQL\n\n## Web 上的声明查询\n\n在 Web 浏览器中，使用声明式 CSS 样式比使用 JavaScript 命令式地操作样式要好得多。类似的，在数据库中，使用 SQL 这样的声明式查询语言比使用命令式查询 API 要好得多。\n\n## 图数据模型\n\n一个图由两种对象组成：顶点（vertices，也称为节点，即 nodes，或实体，即 entities），和边（edges，也称为关系，即 relationships，或弧，即 arcs）。\n![image|675x500](/uploads/image/7f/ee/7fee6d12de516bd22221391ef99b5117bf17c04fa7da24905b41b632a3e58118.avif)\n\nTODO","cooked":"

Chapter2: 数据模型与查询语言

人的想象永远无法挣脱认知的局限

数据模型影响软件的构建方式，也影响问题解决的思考方式。

关系模型与文档模型

\n
关系模型：数据被组织成关系（Table），每个关系是元组（Tuple，Row）的无序集合。
\n

对象关系不匹配

面向对象（OOP）的编程语言被广泛用于应用开发，但是这与 SQL 数据模型之间存在转换的困难，需要引入额外的转换层。

例如，我们可以使用多个表来存储一份简历中会涉及到的内容，如 Position、Education 等，但是实际上对于这样的文档，使用 json 来存储十分方便，它相对于多表模式存在更好的局部性（locality）。

多对一和多对多的关系

有些属性我们并不会选择使用纯文本字符来存储，而是以 ID 来记录。二者的权衡是一个副本（Duplication）问题，ID 信息对人类无意义，但在数据库中有关系映射；文本信息则在每处都对人类有意义。

但是 ID 好处在于永远不需要改变，我们只需要更新其所映射的内容，即可自动更新所有信息，而文本信息则需要对所有的副本进行更改，这难免会产生遗漏，进而产生不一致风险。（去除这样的重复是数据库规范化思想之一，是三大范式的第？范式（忘记了））

在表示多对一和多对多的关系时，关系数据库和文档数据库并没有根本的不同：在这两种情况下，相关项目都被一个唯一的标识符引用，这个标识符在关系模型中被称为外键，在文档模型中称为文档引用

对高度关联的数据而言，文档模型是极其糟糕的，关系模型是可以接受的，而选用图形模型（后文会讲）是最自然的。

文档模型中的模式灵活性

文档数据库有时称为无模式（schemaless），但这具有误导性，因为读取数据的代码通常假定某种结构 —— 即存在隐式模式，但不由数据库强制执行。更精确的术语是读时模式（schema-on-read，数据的结构只在数据被读取时才被解释），相应的是写时模式（schema-on-write，传统的关系数据库方法中，模式明确，且数据库确保所有的数据都符合其模式）。读时模式类似于编程语言中的动态（运行时）类型检查，而写时模式类似于静态（编译时）类型检查。

$\"image\"$

MySQL 在执行 ALTER TABLE 时会复制整个表，这可能意味着在更改一个大型表时会花费几分钟甚至几个小时的停机时间。大型表运行 UPDATE 是一个巨大的开销，我们可以使用读取时填充的策略，类似于第一章中，仅在需要时拉取信息。

数据查询语言

SQL

Web 上的声明查询

在 Web 浏览器中，使用声明式 CSS 样式比使用 JavaScript 命令式地操作样式要好得多。类似的，在数据库中，使用 SQL 这样的声明式查询语言比使用命令式查询 API 要好得多。

图数据模型

一个图由两种对象组成：顶点（vertices，也称为节点，即 nodes，或实体，即 entities），和边（edges，也称为关系，即 relationships，或弧，即 arcs）。
\n $\"image\"$

TODO

\n","createdAt":"2024-04-22 05:24:20.31557","updatedAt":"2024-04-22 05:24:20.31557","replyToPostNumber":null,"replyCount":0,"likeCount":1,"wordCount":1005,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"❤️","count":1,"users":[{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old"}],"hasReacted":false}],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":30937,"postNumber":6,"raw":"感觉直接读这个对我还是有点难，先读一些基础的相关书籍：\n《System Design Interview》Chapter One Review\nhttps://shiny-substance-26b.notion.site/Chapter-one-Scale-from-Zero-to-Millions-of-users-1bfba97f6e4a40f48894e2fab32bd2c4?pvs=4\n欢迎大家评论指出问题！","cooked":"

感觉直接读这个对我还是有点难，先读一些基础的相关书籍：
\n《System Design Interview》Chapter One Review

\n\n欢迎大家评论指出问题！","createdAt":"2024-04-27 12:23:43.96336","updatedAt":"2024-04-27 12:24:24.226794","replyToPostNumber":null,"replyCount":1,"likeCount":1,"wordCount":44,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"❤️","count":1,"users":[{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old"}],"hasReacted":false}],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":30998,"postNumber":7,"raw":"Chapter Two: Back-Of-The-Envelope Estimation\nhttps://shiny-substance-26b.notion.site/Chapter-Two-Back-Of-The-Envelope-Estimation-8fc2a090259e4bdb9a0f51fa064d1d48?pvs=4","cooked":"

Chapter Two: Back-Of-The-Envelope Estimation

\n","createdAt":"2024-04-28 04:48:13.329256","updatedAt":"2024-04-28 04:48:13.329256","replyToPostNumber":6,"replyCount":1,"likeCount":1,"wordCount":5,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"❤️","count":1,"users":[{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old"}],"hasReacted":false}],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":31006,"postNumber":8,"raw":"Chapter Three: A Framework for System Design Interviews\nhttps://shiny-substance-26b.notion.site/Chapter-Three-A-Framework-for-System-Design-Interviews-28b6e3a422b1444cbaee81e89e81e773?pvs=4","cooked":"

Chapter Three: A Framework for System Design Interviews

\n","createdAt":"2024-04-28 06:04:28.635224","updatedAt":"2024-04-28 06:04:28.635224","replyToPostNumber":7,"replyCount":0,"likeCount":1,"wordCount":9,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"❤️","count":1,"users":[{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old"}],"hasReacted":false}],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":31308,"postNumber":9,"raw":"这个书很好，我最近也在读","cooked":"

这个书很好，我最近也在读

\n","createdAt":"2024-05-02 10:05:10.0958","updatedAt":"2024-05-06 06:26:45.130207","replyToPostNumber":null,"replyCount":1,"likeCount":0,"wordCount":12,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old","avatarUrl":"/uploads/image/43/32/4332638c11248b8ff07033c11de0759a55205facfbec85e14458245a91991faf.avif","admin":false,"moderator":false,"signatureRaw":null,"signatureCooked":null}},{"id":31309,"postNumber":10,"raw":"得看原版翻译版太抽象了…………","cooked":"

得看原版翻译版太抽象了…………

\n","createdAt":"2024-05-02 10:07:47.425007","updatedAt":"2024-05-02 10:07:47.425007","replyToPostNumber":9,"replyCount":1,"likeCount":0,"wordCount":12,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":31310,"postNumber":11,"raw":"我英文不好，得靠 Google translate","cooked":"

我英文不好，得靠 Google translate

\n","createdAt":"2024-05-02 11:21:10.705723","updatedAt":"2024-05-06 06:26:45.210293","replyToPostNumber":10,"replyCount":1,"likeCount":0,"wordCount":10,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old","avatarUrl":"/uploads/image/43/32/4332638c11248b8ff07033c11de0759a55205facfbec85e14458245a91991faf.avif","admin":false,"moderator":false,"signatureRaw":null,"signatureCooked":null}},{"id":31313,"postNumber":12,"raw":"我也差不多但是直接看汉语版会麻。。\n\n我英文看不懂导致的困意也不如我看汉语版看得迷迷糊糊产生的困意足。。","cooked":"

我也差不多但是直接看汉语版会麻。。

我英文看不懂导致的困意也不如我看汉语版看得迷迷糊糊产生的困意足。。

\n","createdAt":"2024-05-02 11:29:49.977213","updatedAt":"2024-05-02 11:29:49.977213","replyToPostNumber":11,"replyCount":1,"likeCount":0,"wordCount":48,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":31438,"postNumber":13,"raw":"翻译长篇文字就是很难，得兼具文字和技术素养才能译得好，所以译本这东西良莠不齐实在正常。华章系列里不是也有译得不好的吗。","cooked":"

翻译长篇文字就是很难，得兼具文字和技术素养才能译得好，所以译本这东西良莠不齐实在正常。华章系列里不是也有译得不好的吗。

\n","createdAt":"2024-05-04 05:24:19.602863","updatedAt":"2024-05-04 05:24:19.602863","replyToPostNumber":12,"replyCount":1,"likeCount":0,"wordCount":59,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":1381,"username":"greyishsong","name":"greyishsong","avatarUrl":"/uploads/image/da/bc/dabc731b0311f59850625bbeb55ed969fcfac0430c5ef0f68441e5466b7aa496.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":31440,"postNumber":14,"raw":"是的😭","cooked":"

是的😭

\n","createdAt":"2024-05-04 05:40:54.099729","updatedAt":"2024-05-04 05:40:54.099729","replyToPostNumber":13,"replyCount":0,"likeCount":0,"wordCount":3,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":31459,"postNumber":15,"raw":"ddia 这一版译文的主要问题在于用语过于生涩，加上本身这玩意没几句就要蹦出来几个术语，buff 叠满了非常累。另一方面，通篇指针满天飞，初读连自动解引用都难，更别提想理解就必须解引用强制多态了 :halo:","cooked":"

ddia 这一版译文的主要问题在于用语过于生涩，加上本身这玩意没几句就要蹦出来几个术语，buff 叠满了非常累。另一方面，通篇指针满天飞，初读连自动解引用都难，更别提想理解就必须解引用强制多态了 😇

\n","createdAt":"2024-05-04 13:56:29.109065","updatedAt":"2024-05-04 13:56:29.109065","replyToPostNumber":null,"replyCount":0,"likeCount":0,"wordCount":89,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":1277,"username":"ucw","name":null,"avatarUrl":"/uploads/image/03/ea/03eac2176be50969b549f432e72df28bd719033042da4c6c41c3fde705e8f13a.avif","admin":false,"moderator":false,"signatureRaw":null,"signatureCooked":null}},{"id":33889,"postNumber":16,"raw":"Chapter four: Design A Rate Limiter\nhttps://shiny-substance-26b.notion.site/Chapter-Four-Design-A-Rate-Limiter-f3756b11d3de4bcaa0ef33d9229dff7d?pvs=4","cooked":"

Chapter four: Design A Rate Limiter

\n","createdAt":"2024-05-20 05:19:14.96754","updatedAt":"2024-05-20 05:19:14.96754","replyToPostNumber":null,"replyCount":0,"likeCount":1,"wordCount":7,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"❤️","count":1,"users":[{"id":1288,"username":"LittleWangInShanghai","name":"小王在上海"}],"hasReacted":false}],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}},{"id":33900,"postNumber":17,"raw":"Chapter Five: Design Consistent Hashing\nhttps://shiny-substance-26b.notion.site/Chapter-Five-Design-Consistent-Hashing-3f8c6faa09724d818926afdbc23e046c?pvs=4","cooked":"

Chapter Five: Design Consistent Hashing

\n","createdAt":"2024-05-20 08:17:15.798309","updatedAt":"2024-05-20 08:17:15.798309","replyToPostNumber":null,"replyCount":0,"likeCount":0,"wordCount":6,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":178,"username":"Hypocrisy","name":"rotartsinimdA","avatarUrl":"/uploads/image/ce/f3/cef3773e378e161524cc7523c8a63dff0698d22802b0c1ab669894d395ee36a3.avif","admin":false,"moderator":true,"signatureRaw":null,"signatureCooked":null}}],"hasMore":false,"lastReadPostNumber":1,"hasUrlPostNumber":false}