anchor.diff:  
   image::kafka-qs-architecture.png[alt=Architecture, align=center]
   
  -The first application, the `producer`, will let the user request some quotes over a HTTP endpoint.
  +The first application, the _producer_, will let the user request some quotes over a HTTP endpoint.
   For each quote request a random identifier is generated and returned to the user, to put the quote request on _pending_.
   At the same time the generated request id is sent over a Kafka topic `quote-requests`.
   
   image::kafka-qs-app-screenshot.png[alt=Producer App UI, align=center]
   
  -The second application, the `processor`, in turn, will read from the `quote-requests` topic put a random price to the quote, and send it to a Kafka topic named `quotes`.
  -
  -Lastly, the `producer` will read the quotes and send them to the browser using server-sent events.
  +The second application, the _processor_, in turn, will read from the `quote-requests` topic put a random price to the quote, and send it to a Kafka topic named `quotes`.
  +
  +Lastly, the _producer_ will read the quotes and send them to the browser using server-sent events.
   The user will therefore see the quote price updated from _pending_ to the received price in real-time.
   
   == Solution
  
positive.code: }
  ----
  
  JSON representation of `Quote` objects will be used in messages sent to the Kafka topic
  and also in the server-sent events sent to browser clients.
  
  Quarkus has built-in capabilities to deal with JSON Kafka messages.
  In a following section we will create serializer/deserializer classes for Jackson.
  
  == Sending quote request
  
  Inside the `producer` project locate the generated  `src/main/java/org/acme/kafka/producer/QuotesResource.java` file, and add the following content:
  
  [source,java]
  ----
  
negative.code: == Running in JVM or Native mode
  
  When not running in dev or test mode, you will need to start your Kafka broker.
  You can follow the instructions from the https://kafka.apache.org/quickstart[Apache Kafka website] or create a `docker-compose.yaml` file with the following content:
  
  [source, yaml]
  ----
  