Errata

Foundations of Scalable Systems

Errata for Foundations of Scalable Systems

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Page Page 103
Figure 4-2. Comparing a single-threaded and multithreaded process

Figure 4-2. Comparing a single-threaded and multithreaded process

Misprint on the name for the stack.

It is spelled in Figure 4.2 as "Slack" and not "Stack".

Easy to miss that.

Great book! Thanks a lot.

Note from the Author or Editor:
thx - we'll get it fixed!

 Thomas G. Schaffernoth  Nov 22, 2022  Mar 17, 2023
Page p77.
Figure 3-3

On the TCP side of the diagram, the book has "Resquest + ACK."
Is it a Request or a Response?
There is no such a work Resquest.

Note from the Author or Editor:
thx - it should just read

'Request + ACK'

... one that slipped thru the cracks!

Please correct, and thx again for spotting this!

Ian

 Vlad Bezden  Feb 20, 2023  Mar 17, 2023
Page 296
"Distributed Joins" sidebar

The link for "The myth of NoSQL (vs. RDBMS) “joins don’t scale” blog post." is broken. I found the right post, but I can't include the link for it here.

Note from the Author or Editor:
thx - this is the correct link I believe

https://www.dbi-services.com/blog/the-myth-of-nosql-vs-rdbms-joins-dont-scale/

 Vlad Bezden  Mar 17, 2023 
Page 411
3 paragraph of "Distribution and Replication" chapter

"By default, read operations can access any replica, leading to the potential for stale reads. If you want to ensure you read the latest value of an item, you can set the ConsistentRead parameter in read APIs to true. This directs writes to the leader node, which has the latest value. Strongly consistent reads consume more capacity units than eventually consistent reads and may fail if the leader partition is unavailable."

Shouldn't it be, "This directs read to the leader node, which has the latest value?" The keyword is "read" instead of "write".

Note from the Author or Editor:
thx ... it certainly should say:

"This directs reads to the leader node, which has the latest value?"

 Vlad Bezden  Apr 03, 2023