Kafka for Developers - Data Contracts Using Schema Registry - Build the Coffee Order Consumer

This lecture covers the creation and configuration of a Spring Kafka consumer for coffee orders. It begins with setting up the consumer package and class, adding necessary annotations, and configuring the application.yaml file. The lecture also explains how to test the consumer by publishing messages from a producer and verifying the consumer's ability to read and log these messages. The session concludes with a demonstration of the end-to-end application functionality.

What is the first step in creating a Spring Kafka consumer for coffee orders?

• Set up a database connection.

• Add a 'main' method.

• Create a package named 'consumer'.

• Create a package named 'producer'.

Which annotation is used to ensure the Kafka consumer class is scanned during application startup?

• @Repository

• @Service

• @Entity

• @Component

What is the purpose of the 'onMessage' function in the Kafka consumer?

• To update the Kafka topic configuration.

• To delete messages from the Kafka topic.

• To log messages received from the Kafka topic.

• To send messages to the Kafka topic.

Which file is used to configure the consumer settings such as server port and deserializers?

• application.yaml

• server.config

• consumer.config

• application.properties

What does setting 'auto.offset.reset' to 'latest' ensure?

• Messages are not read at all.

• Messages are read in reverse order.

• Only the latest messages are read.

• All messages are read from the beginning.

How can you verify that the Kafka consumer is correctly reading messages from the topic?

• By running a unit test.

• By observing the log messages.

• By checking the network traffic.

• By checking the database entries.

What is the role of the schema registry in the Kafka consumer setup?

• To handle network requests.

• To store consumer configurations.

• To manage database connections.

• To retrieve the schema for messages.