Event schema design in Microservices - Architecture Diagram

System Overview - Event schema design

This system handles event-driven communication between microservices. It ensures that events are structured with a clear schema for consistency and easy integration. Key requirements include schema validation, versioning, and reliable event delivery.

Architecture Diagram

User
  |
  v
Event Producer Service
  |
  v
Message Broker (Event Bus)
  |
  v
Event Consumer Service
  |
  v
Schema Registry

Components

User

actor

Initiates actions that generate events

Event Producer Service

service

Generates events following a defined schema

Message Broker (Event Bus)

message_queue

Transports events asynchronously between services

Event Consumer Service

service

Receives and processes events based on schema

Schema Registry

service

Stores and manages event schemas for validation and versioning

Request Flow - 6 Hops

User → Event Producer Service

Event Producer Service → Schema Registry

Event Producer Service → Message Broker (Event Bus)

Message Broker (Event Bus) → Event Consumer Service

Event Consumer Service → Schema Registry

Event Consumer Service → Event Consumer Service

Failure Scenario

Component Fails:Schema Registry

Impact:Event validation fails, causing event production and consumption to halt or process invalid data

Mitigation:Use schema caching in services and deploy schema registry with high availability and replication

Architecture Quiz - 3 Questions

Which component ensures that events follow a consistent structure?

A Schema Registry

B Message Broker

C Event Consumer Service

D User

Design Principle

This design shows how a schema registry centralizes event format definitions to ensure consistency and compatibility across microservices. Using a message broker decouples services for scalability and reliability.