wire format
The exact shape data takes when it travels between programs, such as the field names and types of a JSON body.
In more detail
Clients depend on the wire format, not on internal class names, so field names, types and whether fields may be missing are all part of the public contract. Keep wire models separate from storage models so each can change for its own reasons.
Examples
A Kafka broker stores record values in whatever wire format the producer chose.The course uses records such as OrderView as wire models, separate from JPA entities.Related terms
- serialization — Turning an in-memory object into bytes, such as JSON text, that can be sent or stored, and parsing it back again.
- binary encoding — Representing data as raw bytes laid out by a fixed plan rather than as readable text.
- Confluent wire format — The framing that schema-registry serializers put in front of each record: a zero magic byte, then a four-byte big-endian schema ID, then the encoded data.
- API contract — The written promise an API makes about its operations, inputs, outputs and errors, which callers rely on while the code behind it changes.
- breaking change — A change that makes existing users of a program or interface stop working until they change something too.
- response model — A type, often a record, that describes exactly the data an API accepts or returns, separate from database entities.
Taught in
- The Field The Registry Refused — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Pattern Matching And Text Blocks — Modern Java: Virtual Threads & High-Throughput Services
- Serialization And JSON — Modern Java: Virtual Threads & High-Throughput Services
- Working With Jackson — Modern Java: Virtual Threads & High-Throughput Services
- Bytes On The Wire: JSON, Avro And Protobuf — Apache Kafka & Event Streaming
- The Schema Registry — Apache Kafka & Event Streaming