Errata

Data Management at Scale

Errata for Data Management at Scale

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, , Other Digital Version
Page 112
below picture

This text:

1. At the top sit the modern applications, which can be exposed directly via the API gateway. In this pattern the application uses modern communication, such as REST/JSON.
2. In the middle are the legacy applications, which require additional decoupling via the ESB. The service of the ESB can be wrapped into the API gateway.
3. At the bottom sits microservices communication. Microservices communicate internally via the service mesh. APIs, which need to be exposed externally, are decoupled via the API gateway.

Doesn't correspond to the picture. Must be changed into:

1. At the bottom left are the legacy applications, which require additional decoupling via the ESB. The service of the ESB can be wrapped into the API gateway.
2. In the middle sit the modern applications, which can be exposed directly via the API gateway. In this pattern the application uses modern communication, such as REST/JSON.
3. At the right sits microservices communication. Microservices communicate internally via the service mesh. APIs, which need to be exposed externally, are decoupled via the API gateway.

Piethein Strengholt
Piethein Strengholt
 
Feb 09, 2021  Feb 12, 2021
Printed, PDF, ePub
Page 181
Broker / mediators topologies

Hi.

You state that publish/subscribe is a software architecture implementation of the mediator topology.

Then you go on to state: "Unlike the mediator topology, the broker topology model can also be used to implement the publish-subscribe model."

This is confusing and seems to be a contradiction. Please clarify.

Overall, a great book which I greatly enjoy reading.

Best
Oliver

Note from the Author or Editor:
The word "Unlike" should be changed to "Just like". So this sentence:

Unlike the mediator topology, the broker topology model can also be used to implement the publish-subscribe model.

Should be replaced by:

Just like the mediator topology, the broker topology model can also be used to implement the publish-subscribe model.

Oliver Baier  Aug 23, 2020  Feb 12, 2021
Printed, PDF, ePub
Page 263
1st paragraph

Book reads: A practical way to begin implementing MDM into your organization is to start with the simplest implementation style: repository


Repository is not one of the four styles mentioned in the chapter.

Note from the Author or Editor:
A practical way to begin implementing MDM into your organization is to start with the simplest implementation style: repository.

Repository here must be changed to registry.

Samuel Greene  Dec 17, 2020  Feb 12, 2021