Which is a safe practice for event schema evolution?

Problem Statement

Explanation

Add fields with defaults and avoid changing meaning. Consumers should ignore unknown fields. For breaking changes, publish a new version key or topic and migrate gradually. A schema registry helps coordinate producers and consumers.

Code Solution

SolutionRead Only

event { v:2, orderId, total, currency? }

Practice Sets

This question appears in the following practice sets:

Messaging & Event-Driven Architecture

Next Question

Master Interviews
Anywhere, Anytime

Which is a safe practice for event schema evolution?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews Anywhere, Anytime

Which is a safe practice for event schema evolution?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews
Anywhere, Anytime