msgpack vs protobuf: What are the differences?

## Introduction

Here we compare the key differences between msgpack and protobuf.

1. **Data Type Support**: Msgpack supports a wider range of data types including raw binary data, whereas protobuf is more limited in the data types it supports, focusing on specific key data types like integers and strings.
2. **Serialization Size**: Protobuf typically produces smaller serialized data in comparison to msgpack due to its efficient serialization algorithms and schema-based approach.
3. **Schema Definition**: Protobuf requires a predefined schema where message types are defined in a .proto file before data serialization, while msgpack does not rely on any predefined schema for serialization.
4. **Language Support**: Protobuf offers support for a vast number of languages including C++, Java, Python, and more, while msgpack also provides support for multiple languages but may have fewer language bindings compared to protobuf.
5. **Backward Compatibility**: Protobuf emphasizes backward compatibility by allowing new fields to be added to messages without breaking compatibility with existing serialized data, whereas msgpack may not offer as robust backward compatibility features.
6. **Performance**: When it comes to performance, protobuf is known for its fast serialization and deserialization speeds, often outperforming msgpack in benchmarks especially for larger data payloads.

In Summary, msgpack and protobuf differ in data type support, serialization size, schema definition, language support, backward compatibility, and performance. Each has its strengths and is suitable for different use cases based on these key differences.