Encoding Format Advisor

When to Use

You are designing or evolving a system that passes data between processes — over the network, through a message broker, or persisted to disk — and need to choose how to encode that data and how to evolve the schema over time without breaking running services.

This skill applies when:

• You are choosing an encoding format before building or extending a service API
• Your system uses rolling upgrades: new and old versions of code run simultaneously, reading and writing the same data
• You plan schema changes (add field, remove field, rename field, change type) and need to know whether each change is safe
• You are experiencing performance or payload problems with a text-based format and evaluating binary alternatives
• Different teams or services read the same data and cannot all upgrade simultaneously
• You need to store data durably (database, file, Kafka topic) where records outlive the code that wrote them

This skill addresses format selection and schema evolution. For data shape decisions (relational vs. document vs. graph), use data-model-selector first. For stream processing pipeline design using encoded data, see stream-processing-designer.

Context & Input Gathering