Skip to main content

2 posts tagged with "Messages"

View All Tags

Document examples with your schemas

· 5 min read
David Boyne
Founder of EventCatalog

A schema tells you the shape of a message. An example shows you how it can be used.

Schemas are necessary. Examples are what people actually reach for when they're writing a consumer, debugging a failed event, or onboarding to a service they've never touched.

EventCatalog now supports the ability to add any amount of examples with your schemas, helping your teams understand exactly how your messages are used in your architecture.

Introducing query messages for EventCatalog

· 4 min read
David Boyne
Founder of EventCatalog

;

In many distributed architectures, domains and services communicate through different types of messages, typically categorized as events, commands, and queries.

EventCatalog now includes support for documenting queries, allowing you to clearly outline which queries a service accepts and which it invokes. Queries are often seen in protocols such as HTTP and gRPC.