Event schema designer

Define structured event payloads for inter-service communication. Meridian validates every event against your schema at the edge before routing to downstream handlers.

Schema format

Schemas follow the CloudEvents 1.0 specification with optional Meridian extensions for custom attributes, batching hints, and dead-letter policies.

{
  "specversion": "1.0",
  "type": "com.meridian.order.created",
  "source": "/orders",
  "subject": "order-4821",
  "datacontenttype": "application/json",
  "data": {
    "orderId": "ord_9a7f",
    "amount": 2999,
    "currency": "USD"
  }
}

Custom extensions

Add meridianbatch to hint at windowed aggregation, or meridiandlq to route undeliverable events to a dead-letter topic.

Validation rules

• type must be a reverse-DNS string
• source must be a valid URI path
• data must conform to the registered JSON Schema
• Unknown extension keys are dropped silently unless strict mode is enabled