Skip to content

Schema Registry

The KafkaSchemaRegistryHelper wraps @platformatic/kafka's ConfluentSchemaRegistry. It provides a centralized schema registry that auto-serializes/deserializes messages using registered schemas (Avro, Protobuf, JSON Schema).

typescript
class KafkaSchemaRegistryHelper<
  KeyType = string,
  ValueType = string,
  HeaderKeyType = string,
  HeaderValueType = string,
> extends BaseHelper

NOTE

KafkaSchemaRegistryHelper extends BaseHelper directly (not BaseKafkaHelper) -- it has no broker connection or health tracking. It's a configuration wrapper, not a client.

Helper API

MethodSignatureDescription
newInstance(opts)static newInstance<K,V,HK,HV>(opts): KafkaSchemaRegistryHelper<K,V,HK,HV>Factory method
getRegistry()(): ConfluentSchemaRegistry<K,V,HK,HV>Get the registry instance (pass to producer/consumer)
getSerializers()(): Serializers<K,V,HK,HV>Get schema-based serializers
getDeserializers()(): Deserializers<K,V,HK,HV>Get schema-based deserializers

IKafkaSchemaRegistryOptions

typescript
interface IKafkaSchemaRegistryOptions extends ConfluentSchemaRegistryOptions {
  identifier?: string; // Default: 'kafka-schema-registry'
}
OptionTypeDefaultDescription
urlstring--Schema registry URL. Required
auth{ username: string; password: string }--Basic auth credentials
protobufTypeMapperProtobufTypeMapper--Custom Protobuf type mapper
jsonValidateSendboolean--Validate JSON schema on produce
identifierstring'kafka-schema-registry'Scoped logging identifier

What it solves

Without a schema registry, producers and consumers must agree on message shape out-of-band. If the producer changes the shape of value (adds/removes fields), consumers break silently at runtime.

  • Schema Registry is a centralized server (Confluent Schema Registry) that stores and validates schemas.
  • It enforces a contract: the producer says "I want to send this shape", the registry validates it against the registered schema before the message reaches Kafka; the consumer asks "what shape is this?" and the registry tells it how to deserialize.
Without registryWith registry
Message formatRaw string, manual JSON.stringify/JSON.parseTyped object, auto ser/deser
ValidationNone -- runtime crashes on shape driftSchema validated before send
Schema evolutionBreaks consumers silentlyBackward/forward compatibility enforced
Where schemas liveNowhere (tribal knowledge)Centralized server, e.g. http://registry:8081

Use it when you need schema enforcement and compatibility checks across producers/consumers - especially in multi-team environments. Skip it for simple string/JSON messages where both sides are controlled by the same team and format changes are coordinated by hand.

Without vs. with the registry

Without a registry, serialization is entirely manual and unchecked:

typescript
// Producer -- manually serialize
const producer = KafkaProducerHelper.newInstance({
  bootstrapBrokers: ['127.0.0.1:29092'],
  clientId: 'order-producer',
});

await producer.getProducer().send({
  messages: [{
    topic: 'orders',
    key: 'order-1',
    value: JSON.stringify({ id: 1, total: 99.99 }),  // <- just a string, no validation
  }],
});

// Consumer -- manually deserialize, hope the shape is correct
const consumer = KafkaConsumerHelper.newInstance({
  bootstrapBrokers: ['127.0.0.1:29092'],
  clientId: 'order-consumer',
  groupId: 'order-group',
  onMessage: async ({ message }) => {
    const order = JSON.parse(message.value as string);  // <- pray it matches
    console.log(order.id, order.total);
  },
});

If the producer adds { id: 1, total: 99.99, currency: 'USD' } or removes total, the consumer has no way to know until it crashes.

With a registry, both sides pass registry instead of serializers/deserializers:

typescript
import {
  KafkaSchemaRegistryHelper,
  KafkaProducerHelper,
  KafkaConsumerHelper,
} from '@venizia/ignis-helpers/kafka';

// 1. Create registry -- points to Confluent Schema Registry server
const registry = KafkaSchemaRegistryHelper.newInstance({
  url: 'http://localhost:8081',
  // auth: { username: 'user', password: 'pass' },  // optional
});

// 2. Producer -- pass registry, it auto-serializes values using the registered schema
const producer = KafkaProducerHelper.newInstance({
  bootstrapBrokers: ['127.0.0.1:29092'],
  clientId: 'order-producer',
  registry: registry.getRegistry(),
});

await producer.getProducer().send({
  messages: [{
    topic: 'orders',
    key: 'order-1',
    value: { id: 1, total: 99.99 },  // <- object, not string! Registry serializes it
  }],
});
// If the value doesn't match the registered schema -> error BEFORE sending to Kafka

// 3. Consumer -- pass the same registry, it auto-deserializes
const consumer = KafkaConsumerHelper.newInstance({
  bootstrapBrokers: ['127.0.0.1:29092'],
  clientId: 'order-consumer',
  groupId: 'order-group',
  registry: registry.getRegistry(),
  onMessage: async ({ message }) => {
    // message.value is already a typed object, not a raw string
    console.log(message.value.id, message.value.total);
  },
});

await consumer.start({ topics: ['orders'] });

With authentication

typescript
const registry = KafkaSchemaRegistryHelper.newInstance({
  url: 'https://schema-registry.example.com',
  auth: {
    username: 'registry-user',
    password: 'registry-password',
  },
});

Alternative: manual serializers

Instead of passing the full registry to registry, extract serializers/deserializers for manual use alongside serializers/deserializers:

typescript
const registry = KafkaSchemaRegistryHelper.newInstance({
  url: 'http://localhost:8081',
});

// Use serializers directly (instead of registry)
const producer = KafkaProducerHelper.newInstance({
  bootstrapBrokers: ['localhost:9092'],
  clientId: 'my-producer',
  serializers: registry.getSerializers(),
});

const consumer = KafkaConsumerHelper.newInstance({
  bootstrapBrokers: ['localhost:9092'],
  clientId: 'my-consumer',
  groupId: 'my-group',
  deserializers: registry.getDeserializers(),
  onMessage: async ({ message }) => { /* ... */ },
});

See also

  • Kafka Overview - the four helpers, shared health/close API, and the compile-binary caveat
  • Producer - registry as a producer option, plus the manual serializers alternative
  • Consumer - registry as a consumer option, plus the manual deserializers alternative

Files: