Data Serialization Formats and Protocols Data is data only when it can move between systems. Serialization formats define how objects become a string or a binary blob that can be stored, sent, and later reconstructed. Protocols describe how those bytes travel and are organized in networks. Understanding both helps you design cleaner APIs, reliable data lakes, and scalable messaging.
Common formats for payloads
JSON: text-based, human readable, widely supported. Good for open APIs and quick prototyping. XML: verbose but strong in structure, with namespaces and schemas. YAML: readable and friendly for configuration, but can be tricky to parse precisely. MessagePack: binary, compact, drop-in for JSON with similar data types. Protobuf: compact binary, schema-driven, fast; requires a .proto file and code generation. CBOR: binary, compact like JSON, suitable for low-bandwidth apps. Avro: schema-based, good for streaming and data lakes, with forward/backward compatibility. Parquet: columnar format for analytics; less common for API payloads but popular in data warehousing. Protocols and where formats fit
...