Errata

Tod Hanseman should be spelled Tod Hansmann

Lior Gavish is mentioned twice

Note from the Author or Editor:
Please remove the second reference to Lior Gavish in acknowlegements

The line
"That's it! Now let’s look at ways to view data contextually using satellites.'
does not seem to fit in this place

The line should be just below the table 8-18, and above the 'Satelites' paragraph.

Note from the Author or Editor:
This might read better if we move the "That's it! Now let’s look at ways to view data contextually using satellites.' sentence to the end of the Link section, after the sentence that says "Note that we're...". This is the sentence right before the satellite portion begins.

Figure 2-7 under DataOps, the first item should be Automation, not Data Governance.
This would bring figure 2-7 in line with the items in figure 2-8.

Note from the Author or Editor:
Replace "Data Governance" with "Automation" in the diagram.

"...which we discuss at greater length in 'Messages and Streams' on page 167.)" should probably read, "...which we discuss at greater length in 'Message Queues and Event-Streaming Platforms' on page 259.)". In its current form, this is a self-referential breadcrumb, and the preceding paragraphs in the section do not "discuss at greater length," whereas the aforementioned section starting on page 259 does go into more detail. This is a particularly confusing typo due to the section name. Indeed, I did not understand the parenthetical until 100 pages later!

Note from the Author or Editor:
O'Reilly - can we fix this? Thanks.

"Understand how to leverage for efficient extraction." Feels like it should read "Understand how to leverage them for efficient extraction." or "Understand how to leverage indexes for efficient extraction."

Note from the Author or Editor:
Fixed in Atlas branch mlhousley

"from routing messages between microservices ingesting millions of events per second of event data from web, mobile, and IoT applications." This feels like there should be to "to" somewhere in this sentence

Note from the Author or Editor:
Fixed in Atlas on branch mlhousley.

The last sentence of the paragraph reads, "A topic can have zero, one, or multiple producers and customers on most event-streaming platforms."

It should probably read, "A topic can have zero, one, or multiple producers and consumers on most event-streaming platforms."

So, "consumers", not "customers ".

Note from the Author or Editor:
Confirmed. Please correct.

"A topic can have zero, one, or multiple producers and customers on most event-streaming platforms."

Shouldn't customers be consumers ?

"A topic can have zero, one, or multiple producers and consumers on most event-streaming platforms."

"...-should extend up and down the entire stack and support the data engineering and lifecycle."

Not sure the last and is supposed to be there?

Note from the Author or Editor:
Delete the last "and"

In the first paragraph there is a reference to a figure that reads (see Figure 6-3).

It should reference Figure 6-2.

Note from the Author or Editor:
Confirmed

"The storage price goes down from faster/higher performing storage to lower storage"

Shouldn't this be:

"The storage price goes down from faster/higher performing storage to slower storage"

"Make sure the code you write stores the data correctly and doesn't accidentally cause data, memory leaks, or performance issues."

What is meant by "...cause data"?

Note from the Author or Editor:
Edit: "Make sure that your code stores the data correctly and doesn't accidentally cause memory leaks or performance issues."

"The big idea is that rather than relying on asynchronous processing, where a batch process runs for each stage as the input batch closes and certain time conditions are met, each stage of the asynchronous pipeline can process data items as they become available in parallel across the Beam cluster"

Shouldn't the first "asynchronous" be "synchronous" ?

Page 287 "if new events arrive for the use" should be user