Errata

Mastering API Architecture

Errata for Mastering API Architecture

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
PDF Page xxxiv
Table I-1. ADR001 separating attendees from the legacy conference system Status Proposed

The Consequences of this ADR says: The call to the Attendee service will not be out of process and may introduce a latency that will need to be tested.

I think it is an out of process call and "will not be" should be "will be".

Yiping Fan  Oct 14, 2023 
PDF Page 89
Figure 4-1 "C4 Model showing the extraction of the Session service from the conference system"

There is a representation of traffic coming from the Session system into the Attendee system, with the caption "API call to create and retrieve session details". This appears to be incorrect, as the call to Attendee would only be related to Attendee data, not Session data. The Session system might want to retrieve Attendee details, much like the Legacy Conference System is doing, so the label on the traffic from the Session to the Attendee systems should read "API call to retrieve attendee details", or "API call to create and retrieve attendee details" if the creation of attendees is somehow part of the responsibility of the Session system.

Camilo  Jan 28, 2024