The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 54
4th paragraph |
"implementing a distributed tracking system": the author surely means a "distributed tracing system"
|
Ruben Petersen |
Apr 14, 2022 |
| Printed |
Page 60
1st sentence |
A nit-pick ;)
The sentence states "..., we need to design for concurrency and partitioning: concurrency allows for each task to be broken up into smaller pieces, while partitioning is essential for allowing these smaller pieces to be processed in parallel."
This is correct as it seems to be an area where two things benefit each other. I believe it is essentially saying that concurrency (being able to perform tasks in parallel) allows for partitioning, and partitioning is needed to take advantage of performance gains that concurrency allows for. It could be confusing to some readers as the verbiage almost flips the meaning of each word.
Again, I think that it intends to say that concurrently executing partitioned tasks lead to performance gains, and it does. It may be better explained though as you can still partition without concurrency, but you should partition things, and in doing so you can leverage the benefit of concurrency in an entangled manner.
|
Owen Shartle |
Oct 24, 2020 |
| Printed |
Page 71
1st sentence & middle paragraph |
Similar to Owen Shartle's report of concurrency/partitioning on page 60, the mix-up continues here. |||
"we can introduce concurrency so that each task is broken up into smaller pieces" – it is actually partitioning, not concurrency, that breaks up the tasks |||
The last sentence "Together, concurrency and partitioning help ensure that our microservice is optimized for both scalability and partitioning." is also weird – partitioning helps optimize for partitioning.
|
Ruben Petersen |
Apr 14, 2022 |
| PDF, ePub, Mobi |
Page 11905
text |
Typos:
Current:
message broker which will make sure that the data is send to another microservice’s API endpoint. There are several microservice communication
Suggested:
"is send to" should be "is sent to"
Current:
microservice ecosystem. The complexity scales linearly with the number of microservice in the overall ecosystem, and ensuring the availability of not
Suggested:
"of microservice in" should be "of microservices in"
Current:
a service isn’t meeting their SLAs (see Chapter 2, Production-Readiness), all deployment can be postponed if the downtime quota of the service
Suggested:
"all deployment can" should be "all deployments can"
Current:
have a large number of small tasks, we can process then all at the same time by sending them to a
Suggested:
"then all at" should be "them all at"
Current:
scenario and potential catastrophe needs to be identified, and then is needs to be forced to happen in production. Running scheduled
Suggested:
"then is needs" should be "then it needs"
|
Anonymous |
Sep 17, 2019 |