Errata

Building Microservices

Errata for Building Microservices

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.

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
Other Digital Version Examples 11-1 and 11-2

XML has wrongly named closing tags:

<forAccount>1234</account>

Should be </forAccount>.

Anonymous  Oct 05, 2016 
Mobi Page ch2
location 411

In Ch. 2, in section "An Evolutionary Vision for the Architect":

"you off comparing" should be "you of comparing"

Anonymous  Apr 05, 2021 
i
Last paragraph under section "What’s Changed Since The 2nd Edition?" in preface.

In the line
"My hope had been to create a book that was around the same size as the 2nd edition, but find a way to pack more ideas in."

change 2nd edition to 1st edition.

Aravind Srinivasan  Jul 23, 2021 
1
Chapter 1, Section "Modelled Around a Business Domain", 2nd paragraph

The line below seems to be wrong.
"Rolling out a feature that requires changes to more that microservices is expensive."

I guess the author meant
"Rolling out a feature that requires changes to more than one microservice is expensive."

Aravind Srinivasan  Jul 26, 2021 
Mobi Page 2%-6%
During page turn

On my Kindle, the first two page views (denoted 1% and 2%) works flawlessly. However, paging past 2% ends me at a 6% mark, completely jumping past the remainder of the first chapter!

Sami Lamti  Jul 17, 2015 
Printed, PDF, ePub, Mobi, , Other Digital Version Page 14
Line 4 (1st Paragraph)

We aren’t medical doctors or engineers, but nor are we plumbers
or electricians. Instead, we fall into some middle ground, which makes it hard for
society to understand us, or for us to understand where we fit.

--- I didn't like this sentence specifically this undermines the Electrician's or Plumber's work. I understand they do earn less than the Software Developers or Doctors but their job is the foundation of any society that we are currently living in. Without them either we Doctors or SD have to leave our job and do their work. Hollywood used to show the same kind of Stereotype that plumbers 'are' overweight, lazy and dumb workers. We should not ridicule them and time has changed so much that we need to give them respect for what they are and the service they provide to our society !

Anonymous  Sep 30, 2019 
Printed Page 33
4th paragraph

"For the appropriate workloads, an FaaS platform..."

Should this be "a FaaS platform"?

Michael Cook  Nov 27, 2022 
PDF Page 46
Remote Procedure Calls, paragraph 1, the last sentence

"they make a local call look like a remote call" -- this probably should be vice versa: they make a remote call look like a local call.

Anonymous  Dec 01, 2016 
PDF Page 65
Figure 4-5

"New release exposes and additional endpoint" should likely be "New release exposes an additional endpoint"

Reuben Kabel  Feb 24, 2016 
Printed Page 65
Figure 4-5

Given the use of semantic versioning, build b190 (in the third block) implies that we haven't made any incompatible changes to the interface, since the Major version is still 1. However this isn't true, since the old endpoint V1 has been completely removed. Thus, it has to be changed to something like b200.

Additionally, in the second block, there is a minor typo; "and" has to be replaced with "an" additional endpoint

Ioannis Kolaxis  Aug 17, 2017 
Printed Page 107
Figure 6-3

In Figure 6-3 the three boxes on the left are labelled with
- User service build
- Catalog service build
- Invoice service build
(being exactly the same as in the CI server context).

In this figure it would make more sense to re-label these three boxes on the left to:
- User service repo
- Catalog service repo
- Invoice service repo
Each of these repos remains mapped to its respective build.

Manuel Jeckelmann  Oct 19, 2018 
Printed Page 142
Last paragraph, first sentence

"A semantic changes is more problematic."

Perhaps "changes" should be "change".


Michael Cook  Nov 27, 2022 
ePub Page 216
First lines of the chapter introduction

"But when once the FTGO team starts deploying microservices ..."

Anonymous  May 26, 2020 
Printed Page 223
2nd paragraph

"A common example would be to split load for reads..."

Change to "split the load"?

Michael Cook  Nov 27, 2022 
Printed Page 257
ordered list

In the ordered list you have:

"3. Containerizing your microservices it is not pain free,"

The "it" could be removed.

Michael Cook  Nov 27, 2022 
Printed Page 335
4th paragraph, 5th line

"deadlines, a sour goal was to complete"

Space is in the wrong place: "as our goal".

Michael Cook  Nov 27, 2022 
Printed Page 376
3rd paragraph

"a user has only to authenticate themselves only once per session"

One too many "only".

Michael Cook  Nov 27, 2022 
Printed Page 520
1st paragraph, 3rd line

"Within an LOB, all services"

Should this be "Within a LOB"?

Michael Cook  Nov 27, 2022