anchor.diff:  mvn clean package
   ----
   
  -To run the application and all related components (Kafka, Kafka Connect with Debezium, a database), we've created a https://github.com/debezium/debezium-examples/blob/master/kstreams-fk-join/docker-compose.yaml[Docker Compose file],
  +To run the application and all related components (Kafka, Kafka Connect with Debezium, a Postgres database), we've created a https://github.com/debezium/debezium-examples/blob/master/kstreams-fk-join/docker-compose.yaml[Docker Compose file],
   which you can find in the https://github.com/debezium/debezium-examples/tree/master/kstreams-fk-join[debezium-examples] repo.
   To launch all the containers, also building the aggregator container image, run the the following:
   
  
positive.code: We have an aggregator application that will read from the two Kafka topics and process them in a streaming pipeline:
  
  - the two topics are joined on customer id
  - each customer is enriched with its addresses depending upon upsert/delete
  - this aggregated data is written out to a third topic, `customersWithAddressesTopic`
  
  When using the Quarkus extension for Kafka Streams all we need to do for that is to declare a http://www.cdi-spec.org/[CDI producer method],
  which returns the `Topology` of our stream processing application.
  This method must be annotated with `@Produces`, and it must return a `Topology` instance.
  The Quarkus extension is responsible for configuring, starting, and stopping the Kafka Streams engine.
  Now let's take a look at the actual streaming query implementation itself.
  
negative.code: If you aren’t using Prometheus, you have a few options like Datadog, Stackdriver, and others.
  For a detailed guide check the https://github.com/quarkiverse/quarkus-micrometer-registry[Quarkiverse Extensions].
  
  On the other hand, we have https://quarkus.io/guides/microprofile-health[MicroProfile Health] spec, which provides information about the liveness of the application,
  i.e. signalling whether your application is running or not and whether your application is able to process requests.
  To monitor the health status of your existing Quarkus application you can add the `smallrye-health` extension:
  
  