[rabbitmq-discuss] Thrift vs. Protocol Buffers as serialization formats

• Previous message: [rabbitmq-discuss] Preventing Publisher from Consuming Own Messages?
• Next message: [rabbitmq-discuss] Thrift vs. Protocol Buffers as serialization formats
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Anyone care to share their experiences with using either of these
(specificially, as the 'on-the-wire' format for RabbitMQ messages)? In
particular, would be interested to know about:

- Ease of managing the (re)generation of message formats for use
across multiple platforms (in our case, C# and Python)
- Serialisation/Deserialisation performance
- Serialized message size

• Previous message: [rabbitmq-discuss] Preventing Publisher from Consuming Own Messages?
• Next message: [rabbitmq-discuss] Thrift vs. Protocol Buffers as serialization formats
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]