Keymate Logo

Transform Once, Deliver Everywhere—Format-Aware Event Publishing

Keymate's Outbox Publisher transforms and routes events to Kafka topics based on each subscriber's format and delivery rules. Whether your consumers expect JSON or protobuf, compact or enriched formats, or specific schema versions—delivery is always accurate, efficient, and secure.

Transform Once, Deliver Everywhere—Format-Aware Event Publishing

Smart Event Delivery Starts with Subscriber-Aware Transformation

This feature extends the Event Hub with a robust transformation and publishing pipeline. Incoming events (via Subscription API or internal producers) go through the following lifecycle: Format normalization into Keymate internal event model. Topic-based routing decisions driven by subscriber metadata. Per-subscriber transformations into JSON or Protocol Buffers. Field filtering, masking, and enrichment if required. Schema validation (via built-in registry) before publish. Secure delivery to Kafka topics mapped to each subscriber. Built-in retry, dead-letter queue, and audit logging. The result: One event → many shaped, validated, and policy-compliant versions → each delivered to its rightful consumer topic.

Event Transformation & Publishing Pipeline

Intelligent event transformation pipeline that converts single events into multiple subscriber-specific formats with validation, security, and reliable delivery.

Example: Subscriber-aware transformation and delivery to Kafka topics

Key Components:

Format Normalization
Topic Routing
Per-Subscriber Transformation
Schema Validation
Secure Delivery

What Makes It Unique

Per-Subscriber Transformation Rules

Events are transformed based on the specific format and schema needs of each target

JSON & Protobuf Support

Dual format support for modern and legacy consumers

Field Filtering & Masking

Remove or redact sensitive fields before publishing

Enrichment Hooks

Add runtime metadata (e.g., org, session info) to outbound payloads

Schema Registry Validation

Ensures payloads conform to expected Avro/Protobuf schemas

Kafka Topic Routing

Dynamically routes events to topics based on consumer or domain mapping

Reliable Outbox Pattern

Uses database-backed outbox for guaranteed delivery, retry, and audit

Tenant-Aware Publishing

Multi-tenant support with strict topic and schema isolation per tenant

Frequently Asked Questions

Yes. One event can be delivered in both JSON and protobuf formats to different consumers.
You can define transformation rules to redact or remove fields based on event type or consumer.
Yes. The system supports adding organization, session, or source metadata to outbound payloads.
The publisher will reject invalid events, log the failure, and send the message to an error queue for debugging.
Yes. The Outbox Publisher uses reliable outbox and retry mechanisms with exponential backoff.

How to Use This Feature

Follow these steps to set up event transformation and publishing.

Implementation Steps

1

Define your event types and transformation rules per subscriber

2

Register format preferences (JSON/Proto), schemas, and topic routes

3

Emit events via Subscription API or internal Keymate workflows

4

Let Event Hub normalize and prepare events

5

Outbox Publisher handles transformation, schema check, and delivery

6

Monitor delivery status and transformation results in observability panel

ELEVATE YOUR IAM STRATEGY

Ready to Transform Your Keycloak Experience?

Implement fine-grained authorization, multi-tenant infrastructure, and comprehensive security policies with Keymate — built on the Keycloak foundation you already trust.