Glossary · Automation software engineering and architecture
Serialization format
Also known as: Data serialization format, Wire format
German: Serialisierungsformat
In computing, a serialization format is a defined representation for converting in-memory data structures into a sequence of bytes or characters for storage or transmission, and back again, such as JSON, XML, Protocol Buffers or OPC UA Binary.
- Software engineering
In one sentence
A serialization format defines how data structures become bytes or text for storage or transmission, for example JSON, XML or Protobuf.
Example
Machine events are serialized as JSON for the cloud dashboard, while the high-rate vibration data uses a compact binary format to save bandwidth.
Explained in context
Context cards connect this term with others to answer one question. Also in British English and German.
How it applies
- Engineering: Text formats (JSON, XML) are readable and widely supported; binary formats (Protocol Buffers, CBOR, OPC UA Binary) are compact and fast. The choice affects bandwidth, performance and debugging.
- Compatibility: Formats with schemas and explicit rules for optional fields make it easier to evolve messages without breaking consumers.
- Documentation: Interface documentation should name the format and version, the schema, the character encoding and conventions such as units, time zones and number precision. Examples of real payloads help integrators most.
Serialization format vs. data model
A Data model defines what information exists and how it relates. A serialization format defines how instances are written as bytes. The same data model can be serialized in several formats, as with RDF in Turtle or JSON-LD.