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. 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
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Figure 4-6

The box on the left (under Web shop) should read "New endpoint version" instead of "Old endpoint version" In same box, v50 should be v65.

O'Reilly Media, Inc.
 
Feb 25, 2015  Feb 27, 2015
Safari Books Online
http://my.safaribooksonline.com/book/software-engineering-and-development/9781491950340/4dot-integra
1st Paragraph

http://my.safaribooksonline.com/book/software-engineering-and-development/9781491950340/4dot-integration/idp493856_html Integration -> Remote Procedure Calls -> 1st paragraph "All these technologies, however, have the same, core characteristic in that they make a local call look like a remote call." Shouldn't it be the other way round, i.e make a remote call look local?

Note from the Author or Editor:
Confirmed. Text should go from "they make a local call look like a remote call" to "they make a remote call look like a local call". Fixed in ch04 and pushed to atlas.

Rob Winston  Mar 21, 2015  Aug 28, 2015
Printed
Page many

The letters in "e'd", as in the words "we'd" and "he'd", are kerned too close to each other everywhere in the book. Compare to "we'll", "it's" or "isn't".

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Safari Books Online
X
After tittle Getting to Grips with the Problem

It reads "The first step is to take a look at the code itself and see which parts of it read to and write from the database." Should say ...which parts of it read from and write to the database.

Note from the Author or Editor:
Good spot - fixed in git (chapter)

Juan Pablo Urzua Torres  May 23, 2015  Aug 28, 2015
PDF
Page 4
4th paragrath

"With a monolithic application, if I want to try and new programming language, ..." Should be "With a monolithic application, if I want to try 'a' new programming..."

Jimmy Luong  Dec 16, 2014  Jan 30, 2015
PDF
Page 8
3 and 4 paragraphs. Middle of paragrah and 2nd sentance respectivly.

Virtualization is spelled wrong as Virtualisation

Brad Semrad  Jun 13, 2014  Jan 30, 2015
ePub
Page 10
1st paragraph under Shared Libraries

Regarding this parenthetical remark: (which supports scoping and names spaces, so not you JavaScript!) JavaScript does support scoping and namespaces. (If you have doubts, google "Javascript scoping namespaces" and it's pretty obvious within the first few results.) Recommend just removing this remark.

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 14
1st paragraph of Inaccurate comparisons

Arcihtects should be Architects obvious carear progression should be obvious career progression

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 17
2nd paragraph under An Evolutionary Vision for the Architect

Sim city should be Sim City

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 21
last paragraph before Practices

countradict should be contradict

Barett McGavock  Dec 10, 2014  Jan 30, 2015
ePub
Page 21
First sentence of Combining Principles And Practices

One person’s principes are anothers practices. should be One person’s principles are another's practices.

Barett McGavock  Dec 10, 2014  Jan 30, 2015
ePub
Page 21
1st paragraph of Principles

grow it's offering should be grow its offering

Barett McGavock  Dec 02, 2014  Jan 30, 2015
PDF
Page 22
1st paragraph

"FindCustomer takes the first name, surname, and email address." Actually in the code: public Customer findCustomer(String id) throws RemoteException; Not sure if function arguments are defined wrong or FindCustomer should have been createCustomer

Note from the Author or Editor:
Confirmed that this is a problem. The text should change to 'createCustoemr takes the first name...'. Fixed in atlas in ch04.asciidoc

Jeffrey Johnston  Feb 27, 2015  Aug 28, 2015
ePub
Page 23
1st paragraph of The Required Standard

managealbe should be manageable

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 24
1st paragraph under Interfaces

Haivng 20 different styles should be Having 20 different styles

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 25
last sentence, 2nd paragraph under Tailored Service Template

becomes complaint for your context? should be becomes compliant for your context?

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 25
1st paragraph under Tailored Service Template

making sure peolpe should be making sure people

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 26
last paragraph before Exception Handling and Technical Debt

they have to be very diligent in not letting our tendendcy for DRY resulting should be they have to be very diligent to not let our tendency for DRY result

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 27
1st paragraph under Exception Handling and Technical Debt

worth capturing such a decison should be worth capturing such a decision

Barett McGavock  Dec 02, 2014  Jan 30, 2015
ePub
Page 29
1st bullet point

Vision: to esure should be Vision: to ensure

Barett McGavock  Dec 02, 2014  Jan 30, 2015
Printed
Page 49
3rd paragraph

"mitigate some of sins of the past" should be "mitigate some of the sins of the past"

Note from the Author or Editor:
Yep - real problem. Fixed in atlas in ch04.asciidoc

Johannes Laire  Mar 26, 2015  Aug 28, 2015
PDF
Page 59
1rst paragraph

In the first sentence on page 59, especailly should be especially.

Note from the Author or Editor:
Good spot - fixed in git in chapter 4.

Christopher Collins  Apr 27, 2015  Aug 28, 2015
Printed
Page 66
Figure 4-6

The page talks about running different versions of the same service. However, the figure contains two identical versions of the service, which is very confusing. I suspect one of them is meant to be different, with "Old endpoint version" changed to "New endpoint version" and "v50" to "v51".

Note from the Author or Editor:
Looks like this has already been fixed in the latest versions

Johannes Laire  Mar 26, 2015  Feb 27, 2015
Printed
Page 83
last paragraph

"NOSQL" should be spelled "NoSQL"

Note from the Author or Editor:
Fixed - NOSQL should be NoSQL. Fixed in Git in chapter 5.

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed
Page 91-94
Entire pages are missing

My printed copy of Building Microservices says First Printing, Second Release (2015-02-27), and skips right from "But what happens when the insert into the order table works, but the insert into the picking table fails?" at the bottom of page 90 on the left page to "What if our application data is better modeled as a graph, as in Neo4j?" at the top of page 95 on the right. Pages 91-94 are completely missing.

Note from the Author or Editor:
Responded to customer and will send a replacement copy. --O'Reilly

Christopher Wood  Jan 27, 2016 
Printed, PDF
Page 105
pg 105-107, Figures 6-1, 6-2, 6-3

Each figure features three boxes representing services on the right. In each picture they say from top to bottom: User service Catalog service Catalog service But they should say: User service Catalog service Invoice service

O'Reilly Media, Inc.
 
Mar 13, 2015  Feb 27, 2015
Printed
Page 109
2nd last paragraph

"nodeJS" should be spelled "Node.js"

Note from the Author or Editor:
Legit problem - fixed in atlas in ch06.

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed
Page 124
last paragraph

"On Linux, process are run" should be "On Linux, processes are run"

Note from the Author or Editor:
Good spot, fixed in Git (chapter 6)

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed
Page 140
2nd paragraph

"so too do the number of moving parts" should be "so too does the number of moving parts"

Note from the Author or Editor:
Looks straightforward! Fixed in git as per the user submitted errata (chapter 7).

Johannes Laire  Mar 26, 2015  Aug 28, 2015
ePub
Page 153
1st Paragraph

In paragraph "Use Semantic Versioning", a sentence towards the end of the paragraph reads as "I haven't see this approach". It should have been "I haven't seen this approach".

Vinay Vishal  Oct 21, 2015  Jan 29, 2016
Printed
Page 153
4th bullet point in the chapter summary

The bullet point reads: "Try to understand the trade-off between putting more efforts into testing and detecting issues faster in production (optimizing for MTBF versus MTTR). It is likely that "efforts" should be "effort" in that sentence.

Stan Ng  Dec 09, 2015  Jan 29, 2016
Printed
Page 159
2nd paragraph

"the avergage CPU load" should be "the average CPU load"

Note from the Author or Editor:
Good spot: "the avergage CPU load" should be "the average CPU load" Fixed in git in chapter 8

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed
Page 164
2nd paragraph

"event-drive architecture patterns" should be "event-driven architecture patterns".

Stan Ng  Dec 09, 2015  Jan 29, 2016
Printed
Page 178
1st paragraph

"Calls made between the browser and server calls" should be "Calls made between the browser and server"

Note from the Author or Editor:
Good spot. "Calls made between the browser and server calls can be" should be "Calls made between the browser and server can be" Fixed in git

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed
Page 183
last paragraph

"SeLinux" should be "SELinux"

Note from the Author or Editor:
Good spot : "SeLinux" should be "SELinux" Fixed in git (chapter 9)

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed
Page 184
1st paragraph

"A new option is GrSSecurity, which aims to be simpler to use than either AppArmour and GrSecurity" 1) "AppArmour" should be spelled "AppArmor" 2) "GrSecurity" should be spelled "grsecurity" 3) the end of the quote should be "than either AppArmor or SELinux"

Note from the Author or Editor:
Original submission is correct - all fixed in git in chapter 9.

Johannes Laire  Mar 26, 2015  Aug 28, 2015
PDF
Page 184
2nd paragraph

The paragraph reads: "[...] which aims to be simpler to use than either AppArmour or GrSecurity [...]" GrSecurity should be substituted with SELinux

Note from the Author or Editor:
"A newer option is GrSSecurity, which aims to be simpler to use than either AppArmour or GrSecurity while also trying to expand on their capabilities" should read "A newer option is GrSecurity, which aims to be simpler to use than either AppArmour or SELinux while also trying to expand on their capabilities" Fixed in git in chapter 9.

Mirco Sanguineti  May 20, 2015  Aug 28, 2015
Printed
Page 212
2nd last paragraph

"a asynchronous" should be "an asynchronous"

Note from the Author or Editor:
Error is correct - fixed in git. "a asynchronous" should be "an asynchronous"

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed
Page 217
2nd last paragraph

"in Chapter 4, but also" should be "in Chapter 4), but also"

Note from the Author or Editor:
Missing bracket after the chapter reference. Fixed in atlas in ch11.asciidoc

Johannes Laire  Mar 26, 2015  Aug 28, 2015
ePub
Page 219
Chapter 6, last paragraph before "Service Configuration" heading

The word "artifact" is misspelled. “Managing environments for single-artfact monolithic systems can be challenging,” Excerpt From: Newman, Sam. “Building Microservices.” O'Reilly Media, Inc., 2015-01-30. iBooks. This material may be protected by copyright.

Note from the Author or Editor:
Confirmed. Text should read 'single-artifact monolithic..." Fixed in atlas in ch06.asciidoc.

Nathan Williams  Mar 21, 2015  Aug 28, 2015
Printed
Page 227
2nd last paragraph

"traffic doesn't go halfway round the world when it needs to" the end should be "when it doesn't need to"

Note from the Author or Editor:
Fixed in atlas in ch11 From "making sure that traffic doesn't go halfway round the world when it needs to" should be "making sure that traffic doesn't go halfway round the world when it doesn't need to"

Johannes Laire  Mar 26, 2015  Aug 28, 2015
Printed, PDF
Page 243
the last sentence of the 1st paragraph

But if you’re using hypermedia and can’t justify the switch, I’d definitely suggest giving Swagger a go. I guess it should be But if you aren't using hypermedia and can’t justify the switch, I’d definitely suggest giving Swagger a go.

Note from the Author or Editor:
Yup - problem. Instead of: "my recommendation is to go with HAL over Swagger. But if you're using hypermedia and can't justify the switch, I'd definitely suggest giving Swagger a go." Should be: "my recommendation is to go with HAL over Swagger. But if you're not using hypermedia and can't justify the switch, I'd definitely suggest giving Swagger a go." Already fixed in atlas in ch11

Kamil Korzekwa  May 13, 2015  Aug 28, 2015