liveBook · Manning

Tagged field

As explained in Microservices Patterns, Second Edition

A tagged field is a serialized message field identified by a numeric identifier rather than only by position or name.

A tagged field is identified in a serialized message by a numeric tag. Protocol Buffers uses tags so a consumer can parse a message even when its local schema lacks fields or has been updated; it can skip unknown tags. section 8.1.6

This differs from Avro, which encodes fields without identifiers and relies on the writer’s schema for field order and types. Avro messages are more compact, but consumers need the correct schema to deserialize them. section 8.1.6

How Microservices Patterns, Second Edition covers it

How deep it goes
Explains numeric identifiers and unknown-tag skipping, without detailing tag assignment.
Examples
Contrasts Protocol Buffers tag-based parsing with Avro’s reliance on the writer’s schema.
What you can do after
Understand how numeric tags let consumers skip unknown fields when local schemas differ.
How it connects
Connects tagged fields to Protocol Buffers and serialized messages, contrasting them with Avro’s schema-dependent field ordering.

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.