Back to Catalog
Integration
Message Construction
Format Indicator
Tell the receiver how to parse the message — format type baked into the header.
Intent & Description
Real-world Use Case
Kafka topic receives messages from 3 producers — one sends JSON v1, one JSON v2, one Avro. Each message has contentType and schemaVersion headers. Consumers check headers and route to the right deserializer. No format guessing, no deserialization explosions.
Source
📌 TL;DR
Format Indicator = content-type header for your messages. Tell the receiver what it is looking at before it tries to parse it. Essential for multi-format or evolving message schemas.
Advantages
- Enables format flexibility and schema evolution on a single channel
- Consumers are self-routing — they pick the right deserializer
- Supports mixed-format channels during migrations
- Pairs well with schema registries (Confluent Schema Registry)
Disadvantages
- Every message carries extra metadata
- Consumers must implement format negotiation logic
- No standard field name across all brokers — teams must agree on conventions
- Stale consumers may not handle new format indicators gracefully