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

使用 Avro 定义模式

学习使用 Apache Avro 定义事件模式。Avro 是一种紧凑且高效的数据序列化框架。

第 2 / 4 课12 个步骤

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

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

What is Apache Avro?

Welcome! In this lesson, we'll explore Apache Avro, a powerful data serialization system. It's widely used in event-driven architectures, especially with Kafka.

Avro helps define the structure of your data (events) using a schema. This schema acts like a blueprint, ensuring consistency and enabling seamless communication between different applications.

Why Use Avro Schemas?

Avro's schema-driven approach offers several benefits:

Data Compactness: Avro serializes data efficiently, leading to smaller message sizes.
Schema Evolution: It provides robust rules for how schemas can change over time without breaking old applications.
Language Agnostic: Schemas are language-independent, allowing different programming languages to read and write the same data.
Strong Typing: Ensures data types are consistent, reducing runtime errors.

Avro Schema Structure

Avro schemas are defined using JSON. Each schema describes a data structure, most commonly a record type.

Key elements of an Avro schema include:

type: The kind of schema (e.g., "record", "enum", "array").
name: The name of the schema (e.g., "User", "Order").
namespace: An optional string to qualify the name.
fields: For record types, an array of field definitions.

Avro Primitive Types

Avro supports a set of basic, primitive data types:

null: No value.
boolean: true or false.
int: 32-bit signed integer.
long: 64-bit signed integer.
float: Single precision (32-bit) floating-point number.
double: Double precision (64-bit) floating-point number.
bytes: Sequence of 8-bit unsigned bytes.
string: Unicode character sequence.

Defining a Simple Record

Let's define a simple Avro record schema for a User. Each field needs a name and a type.

Here, id is an int and name is a string.

{
  "type": "record",
  "name": "User",
  "namespace": "com.coddykit.avro",
  "fields": [
    {"name": "id", "type": "int"},
    {"name": "name", "type": "string"}
  ]
}

Complex Type: Nested Records

You can define complex data structures by nesting records. For example, an Order record might contain a Customer record within one of its fields.

{
  "type": "record",
  "name": "Order",
  "namespace": "com.coddykit.avro",
  "fields": [
    {"name": "orderId", "type": "string"},
    {"name": "customer", "type": {
      "type": "record",
      "name": "Customer",
      "fields": [
        {"name": "customerId", "type": "int"},
        {"name": "email", "type": "string"}
      ]
    }}
  ]
}

Complex Types: Arrays and Maps

Avro also supports collection types:

array: For a list of items of the same type. The items property specifies the type of elements.
map: For key-value pairs, where keys are always strings. The values property specifies the type of values.

{
  "type": "record",
  "name": "Product",
  "namespace": "com.coddykit.avro",
  "fields": [
    {"name": "productId", "type": "string"},
    {"name": "tags", "type": {"type": "array", "items": "string"}},
    {"name": "attributes", "type": {"type": "map", "values": "string"}}
  ]
}

Complex Type: Enums

An enum defines a fixed set of named values. This is useful for fields with a limited, predefined set of options.

The symbols property lists all allowed string values for the enum.

{
  "type": "record",
  "name": "Payment",
  "namespace": "com.coddykit.avro",
  "fields": [
    {"name": "transactionId", "type": "string"},
    {"name": "status", "type": {
      "type": "enum",
      "name": "PaymentStatus",
      "symbols": ["PENDING", "COMPLETED", "FAILED"]
    }}
  ]
}

Complex Type: Unions & Nullables

A union allows a field to be one of several specified types. This is crucial for defining optional or nullable fields.

To make a field nullable, you define its type as a union of "null" and its actual type, e.g., ["null", "string"]. The first type in the union is often the default if not explicitly set.

{
  "type": "record",
  "name": "LogEntry",
  "namespace": "com.coddykit.avro",
  "fields": [
    {"name": "timestamp", "type": "long"},
    {"name": "message", "type": "string"},
    {"name": "userId", "type": ["null", "string"], "default": null}
  ]
}

Setting Default Field Values

You can specify a default value for a field. This is particularly important for schema evolution, as it ensures that older data (without the new field) can still be read without error, using the default value.

The default value must be a valid instance of the field's type.

{
  "type": "record",
  "name": "Settings",
  "namespace": "com.coddykit.avro",
  "fields": [
    {"name": "theme", "type": "string", "default": "dark"},
    {"name": "notificationsEnabled", "type": "boolean", "default": true}
  ]
}

Avro Schema Question

Consider an Avro record for an event. We need a field named comment that can contain a string but is optional (can be null) and defaults to null if not provided.

在交互式课程中回答

Avro Definition Recap

Great job! You've learned the fundamentals of defining schemas with Apache Avro.

Avro schemas are JSON-based blueprints for your data.
They support primitive types (int, string, etc.) and complex types (records, arrays, maps, enums, unions).
Unions are key for defining nullable or optional fields.
Default values are crucial for backward compatibility and schema evolution.

Next, we'll see how to integrate these schemas with Spring Boot and Schema Registry.

免费开始

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

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

课程: 12
课程: 48

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

常见问题解答

「使用 Avro 定义模式」课时是免费的吗？

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

「使用 Avro 定义模式」这节课中我会学到什么？

学习使用 Apache Avro 定义事件模式。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) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「使用 Avro 定义模式」课时需要多长时间？

大多数 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)