Event schema design in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an event schema in microservices?

An event schema defines the structure and format of data sent in an event message between microservices. It ensures all services understand the event data consistently.

intermediate

Why is versioning important in event schema design?

Versioning allows changes to event schemas without breaking existing consumers. It helps services evolve independently while maintaining compatibility.

beginner

Name two common formats used for event schemas.

JSON and Avro are common formats for event schemas. JSON is human-readable, while Avro is compact and supports schema evolution.

intermediate

What is the role of a schema registry in event-driven systems?

A schema registry stores and manages event schemas centrally. It helps producers and consumers validate and evolve schemas safely.

advanced

How can you ensure backward compatibility in event schema changes?

To ensure backward compatibility, add new optional fields instead of removing or changing existing ones. Consumers can ignore unknown fields safely.

What does an event schema primarily define?

A The structure of event data

B The network protocol used

C The database schema

D The UI layout

An event schema defines the structure and format of the event data sent between services.

Which format is NOT commonly used for event schemas?

A Avro

B Markdown

C XML

D JSON

Markdown is a text formatting syntax, not used for event schemas.

Why use a schema registry in microservices?

A To store and manage event schemas centrally

B To store user credentials

C To manage UI components

D To monitor network traffic

A schema registry helps manage event schemas centrally for validation and evolution.

What is a safe way to change an event schema without breaking consumers?

A Remove existing fields

B Change field types

C Rename fields

D Add new optional fields

Adding new optional fields keeps old consumers working without errors.

Versioning in event schemas helps to:

A Encrypt event data

B Prevent any schema changes

C Allow schema changes without breaking consumers

D Improve network speed

Versioning allows schemas to evolve while keeping compatibility.

Explain what an event schema is and why it matters in microservices.

Think about how services understand each other when sending messages.

Describe best practices for evolving event schemas without breaking existing consumers.

Consider how to keep old and new services working together smoothly.