Now, we will recap the steps of our processing engine for Monedero. The customer consults the ETH price in the client's browser and is sent to Kafka through some HTTP event collector.

The first step in our flow is the event correctness validation; remember from the previous chapter that the messages with defects are derived from bad data and that is why they are filtered. The second step now is to enrich our message with geographic location information.

Here are the architecture steps for the Monedero processing engine:

1. Read the individual events from a Kafka topic called input-messages
2. Validate the message, sending any defective event to a dedicated Kafka topic called invalid-messages
3. Enrich the message with the geographic location data
4. Write the enriched messages in a Kafka topic called valid-messages

All of these steps of the second version of...