[rabbitmq-discuss] Thrift vs. Protocol Buffers as serialization formats
SimonT
(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
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq...@lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Marek Majkowski
> 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
In my projects the performance of (de)serialization doesn't matter
that much. But flexibility and simplicity matters a lot.
I tend to use JSON and I'm happy with it. Language support is
brilliand, it's simple and fast enough.
Cheers,
Marek
Abhishek Kona
We use Thrift as a thin layer infront of RabbitMQ to provide Amazon SQS
(acknowledge without keeping a channel open). like semantics for our
queue system.
It has been working like a charm for us.
We primarily use in Java and PHP.
Serialization has never been observed as a major bottleneck in our
application.
So any of PB or Thrift should be good for you. (We use Thrift for its
good RPC capabilities).
The people at https://github.com/eishay/jvm-serializers/wiki/ have
profiled lot of available data serialization methods, you can have a look.
-Abhishek Kona