Advanced Spring Boot 4: Event-Driven Architecture (Kafka) · 강의

Spring Boot와 스키마 레지스트리 통합

Confluent Schema Registry를 Spring Boot Kafka 애플리케이션과 통합하여 Avro 직렬화와 역직렬화를 자동으로 처리합니다.

Spring Boot와 스키마 레지스트리 통합은(는) CoddyKit의 무료 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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.

자주 묻는 질문

“Spring Boot와 스키마 레지스트리 통합” 강의는 무료인가요?

네 — “Spring Boot와 스키마 레지스트리 통합” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의 전체를 잠금 해제할 수 있습니다. 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)을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Advanced Spring Boot 4: Event-Driven Architecture (Kafka)을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.

“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)(으)로 돌아가기