| Author |
Message |
< RabbitMQ mailing list ~ Encoding message payload for multiple languages |
| gar1t |
 Posted: Thu Dec 31, 2009 7:18 pm |
 |
|
|
User
Joined: 11 Aug 2009
Posts: 55
|
I'm curious what others here use for encoding message payload for
cross-language consumption.
I've used Thrift for quite some time, and it's quite nice I think, but
there's the annoying overhead of IDL maintenance, compiling and
distributing application specific client code, etc.
JSON is an obvious choice, but incurs a pretty high overhead for
encoding/decoding.
XML is similar to JSON in terms of pluses and minuses.
There's Protobuf, which seems like a possibly simpler alternative to
Thrift, but still requires IDL maintenance, etc.
Binary representation of Erlang terms is darned near perfect (fast and
flexible), but it's not as easy to consume from other language
environments.
CSV might be a good approach for some applications.
Obviously there's no "one way" here, but I'm curious what others are doing.
Garrett
P.S. Happy New Year!
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
 
|
| Guest |
| Posted: Thu Dec 31, 2009 7:36 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Thu Dec 31, 2009 7:42 pm |
|
|
|
Guest
|
Fudge is also quite interesting:
http://kirkwylie.blogspot.com/2009/11/announcing-release-of-fudge-messaging.html
On Thu, Dec 31, 2009 at 7:17 PM, Garrett Smith <g@rre.tt> wrote:
> I'm curious what others here use for encoding message payload for
> cross-language consumption.
>
> I've used Thrift for quite some time, and it's quite nice I think, but
> there's the annoying overhead of IDL maintenance, compiling and
> distributing application specific client code, etc.
>
> JSON is an obvious choice, but incurs a pretty high overhead for
> encoding/decoding.
>
> XML is similar to JSON in terms of pluses and minuses.
>
> There's Protobuf, which seems like a possibly simpler alternative to
> Thrift, but still requires IDL maintenance, etc.
>
> Binary representation of Erlang terms is darned near perfect (fast and
> flexible), but it's not as easy to consume from other language
> environments.
>
> CSV might be a good approach for some applications.
>
> Obviously there's no "one way" here, but I'm curious what others are doing.
>
> Garrett
>
> P.S. Happy New Year!
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss@lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Dec 31, 2009 7:51 pm |
|
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jan 03, 2010 8:37 am |
|
|
|
Guest
|
On 12/31/09 11:35 AM, Jeremy Dunck wrote:
>
>
> On Dec 31, 2009, at 1:17 PM, Garrett Smith <g@rre.tt> wrote:
>> Binary representation of Erlang terms is darned near perfect (fast and
>> flexible), but it's not as easy to consume from other language
>> environments.
>>
>
> Have you seen Bert?
> http://github.com/blog/531-introducing-bert-and-bert-rpc
>
Another vote for BERT. I'm using it quite happily:
http://github.com/b/bertrem . Piece of cake to encode/decode as
evidenced by the proliferation of client libraries.
b
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jan 03, 2010 8:38 am |
|
|
|
Guest
|
On 12/31/09 11:51 AM, Alexis Richardson wrote:
> On Thu, Dec 31, 2009 at 7:35 PM, Jeremy Dunck <jdunck@gmail.com> wrote:
>>
>>
>> On Dec 31, 2009, at 1:17 PM, Garrett Smith <g@rre.tt> wrote:
>>> Binary representation of Erlang terms is darned near perfect (fast and
>>> flexible), but it's not as easy to consume from other language
>>> environments.
>>>
>>
>> Have you seen Bert?
>> http://github.com/blog/531-introducing-bert-and-bert-rpc
>
> And not wholly unrelatedly: http://github.com/b/bertem
>
FYI, I inconveniently changed the name to bertrem so it could be
pronounced as a name, as is the case with most other BERT bits. Also
for the lulz.
http://github.com/b/bertrem
b
Post received from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
