Advanced Spring Boot 4: Event-Driven Architecture (Kafka) · 课时

Spring Boot 与模式注册中心集成

将 Confluent Schema Registry 集成到 Spring Boot Kafka 应用中，以自动处理 Avro 的序列化和反序列化。

第 3 / 4 课12 个步骤

Spring Boot 与模式注册中心集成 是 CoddyKit 上的免费 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Welcome to Schema Registry Integration

In previous lessons, you learned about the importance of schema management and how to define schemas using Apache Avro. Now, it's time to bring it all together!

This lesson will guide you through integrating the Confluent Schema Registry with your Spring Boot Kafka applications. This integration automates Avro serialization and deserialization, making your data pipelines robust and easy to manage.

What is Confluent Schema Registry?

The Confluent Schema Registry is a standalone service that provides a centralized repository for Avro schemas. It acts as a gatekeeper, ensuring that all data flowing through your Kafka topics conforms to predefined schemas.

It stores a versioned history of all your schemas.
It provides a RESTful interface for registering and retrieving schemas.
It assigns a unique ID to each registered schema.

This central management is key for evolving schemas without breaking older applications.

How It Works with Kafka

When using the Schema Registry with Kafka:

Producers send messages, first registering their Avro schema with the Registry if it's new. They then include a small schema ID in the message payload (or header) along with the serialized Avro data.
Consumers receive messages, extract the schema ID, and fetch the corresponding schema from the Registry. They then use this schema to correctly deserialize the Avro data.

This process is largely transparent to your application code once configured correctly.

Adding Dependencies for Avro

To enable Avro serialization/deserialization with Spring Kafka and the Schema Registry, you need to add specific dependencies to your project. For Maven, this typically involves the kafka-avro-serializer library.

Here are the key dependencies:

spring-kafka: Core Spring Kafka functionality.
kafka-avro-serializer: Confluent's Avro serializer/deserializer.
avro: Apache Avro core library.

You'll also need to configure a plugin (like avro-maven-plugin) to generate Java classes from your .avsc schema files.

Configuring Schema Registry Client

Spring Boot needs to know where your Confluent Schema Registry is running. You specify this in your application.properties or application.yml file.

The property spring.kafka.properties.schema.registry.url is crucial. Let's look at an example:

spring.kafka.bootstrap-servers=localhost:9092
spring.kafka.producer.key-serializer=org.apache.kafka.common.serialization.StringSerializer
spring.kafka.producer.value-serializer=io.confluent.kafka.serializers.KafkaAvroSerializer
spring.kafka.consumer.key-deserializer=org.apache.kafka.common.serialization.StringDeserializer
spring.kafka.consumer.value-deserializer=io.confluent.kafka.serializers.KafkaAvroDeserializer
spring.kafka.properties.schema.registry.url=http://localhost:8081

Defining Our Avro Message Class

Before we send or receive Avro messages, we need an Avro schema and a corresponding Java class. Typically, you'd define a .avsc file and use a build plugin to generate the Java class.

For our example, let's imagine we have a simple User Avro schema. This would generate a Java class like com.coddykit.User with fields like name and age. We'll use this generated class directly in our Spring Boot code.

Producer-Side Avro Serialization

Once your Spring Boot application is configured with the Avro serializer and the Schema Registry URL, sending Avro messages is straightforward. The KafkaTemplate automatically handles the serialization and interaction with the Schema Registry.

Here's a simplified example of a Spring Boot producer sending a User object:

package com.coddykit.producer;

import com.coddykit.User;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.core.KafkaTemplate;

@SpringBootApplication
public class AvroProducerApplication implements CommandLineRunner {

    @Autowired
    private KafkaTemplate<String, User> kafkaTemplate;

    public static void main(String[] args) {
        SpringApplication.run(AvroProducerApplication.class, args);
    }

    @Override
    public void run(String... args) throws Exception {
        String topic = "users-avro-topic";
        User user = new User("Alice", 30);
        kafkaTemplate.send(topic, "user-key-1", user);
        System.out.println("Sent Avro User: " + user);
    }
}

// Simplified User class for demonstration (generated from Avro schema)
// public class User { 
//    private String name; 
//    private int age; 
//    public User(String name, int age) { this.name = name; this.age = age; } 
//    public String getName() { return name; } 
//    public int getAge() { return age; } 
//    @Override public String toString() { return "User{" + "name='" + name + '\'' + ", age=" + age + '}'; } 
// }

Consumer-Side Avro Deserialization

Similarly, on the consumer side, Spring's @KafkaListener, combined with the Avro deserializer and Schema Registry configuration, automatically converts the incoming Avro message bytes into your Java Avro object.

You just specify the target Avro class type in your listener method signature.

package com.coddykit.consumer;

import com.coddykit.User;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.KafkaListener;

@SpringBootApplication
public class AvroConsumerApplication {

    public static void main(String[] args) {
        SpringApplication.run(AvroConsumerApplication.class, args);
    }

    @KafkaListener(topics = "users-avro-topic", groupId = "avro-group")
    public void listen(User user) {
        System.out.println("Received Avro User: " + user);
    }
}

Handling Schema Evolution

One of the most powerful benefits of using the Schema Registry with Avro is its support for schema evolution. As your application needs change, you might need to add, remove, or modify fields in your Avro schemas.

The Schema Registry helps ensure that even if a producer sends data with a newer schema version, older consumers (and vice-versa) can still process the messages without errors, provided the schema changes are compatible (e.g., adding a field with a default value).

Key Benefits of Integration

Integrating the Confluent Schema Registry with Spring Boot Kafka applications brings several significant advantages:

Data Compatibility: Ensures producers and consumers always agree on data format, preventing deserialization errors.
Schema Evolution: Gracefully handles schema changes over time.
Reduced Boilerplate: Automatic serialization/deserialization means less manual code.
Centralized Management: A single source of truth for all your event schemas.
Strong Typing: Leveraging Avro's strong typing for better data quality and developer experience.

Quick Check: Schema Registry Purpose

What is the primary role of the Confluent Schema Registry when integrated with Spring Boot Kafka applications using Avro?

在交互式课程中回答

Recap: Seamless Avro with Spring

Great job! You've learned how to integrate the Confluent Schema Registry with your Spring Boot Kafka applications. This powerful combination automates Avro serialization and deserialization, making your event-driven microservices more robust and maintainable.

We covered the role of the Schema Registry and how it works.
You saw how to configure Spring Boot for Avro and Schema Registry.
We explored producer and consumer examples for seamless Avro object handling.
We touched upon the benefits of schema evolution and data compatibility.

By leveraging the Schema Registry, you ensure that your data contracts are always honored, even as your applications evolve.

免费开始

用 AI 导师学习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「Spring Boot 与模式注册中心集成」课时是免费的吗？

是的 — 「Spring Boot 与模式注册中心集成」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程的其余内容，请升级到 CoddyKit PRO。 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程共包含 4 节课。

「Spring Boot 与模式注册中心集成」这节课中我会学到什么？

将 Confluent Schema Registry 集成到 Spring Boot Kafka 应用中，以自动处理 Avro 的序列化和反序列化。你通过在浏览器中直接运行的动手代码来练习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「Spring Boot 与模式注册中心集成」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课中编写并运行代码吗？

能。每节 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)