Comments on: MsgPack vs. JSON: Cut your client-server exchange traffic by 50% with one line of code http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/ apps, indie & beyond Sun, 20 Oct 2019 13:54:00 +0000 hourly 1 https://wordpress.org/?v=4.0.38 By: earonesty http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-52542 Tue, 15 Oct 2019 21:38:00 +0000 http://indiegamr.com/?p=72#comment-52542 Current version of msgpack supports utf8 fine. And node version is back to faster than JS again.

]]> By: Fabio A. http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-52463 Wed, 11 May 2016 12:45:00 +0000 http://indiegamr.com/?p=72#comment-52463 Why so? Can’t the client just set “Content-Encoding: gzip” and be done with it (assuming the server knows how to deal with that content encoding)?

]]> By: nacmartin http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-52435 Thu, 19 Mar 2015 18:48:00 +0000 http://indiegamr.com/?p=72#comment-52435 Hi Nathan. did you do that MsgPack vs JSON in Erlang test? What were the results?

]]> By: Thiago Z S http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-22358 Wed, 25 Sep 2013 15:32:34 +0000 http://indiegamr.com/?p=72#comment-22358 In my point of view, we have a problem with the messagepack, I think the API dosent have a support to compress all over the data.
I dont understand why the messagepack dont compress the json. Maybe I doing some wrong.
Just for fun, I’m and Will, we doing some tests over Redis with a list with one object serialized! Checkout our tests.

https://gist.github.com/thiagozs/6701223

Thanks all

]]> By: Pavel http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-13663 Tue, 16 Apr 2013 23:36:17 +0000 http://indiegamr.com/?p=72#comment-13663 Thanx for the benchmark, nathan!

]]> By: 2012 Archive of Hanselman's Newsletter of Wonderful Things - Scott Hanselman http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-5006 Tue, 08 Jan 2013 01:55:17 +0000 http://indiegamr.com/?p=72#comment-5006 […] looking into MsgPack as a smaller alternative to JSON. Is it worth the […]

]]> By: Nathan Aschbacher http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-79 Mon, 18 Jun 2012 03:01:06 +0000 http://indiegamr.com/?p=72#comment-79 I did a little speed comparison of the node.js msgpack implementations here: https://gist.github.com/2946474

It’s a very basic benchmark, but it’s pulled from the node-msgpack project that makes some speed claims of its own vs. JSON.

Clearly JSON parsing and encoding got much, much faster at some point in V8, but msgpack is about the same speed as it always was. JSON is 4+ times as fast now.

I need to do a test on MsgPack vs. JSON in Erlang next.

]]> By: Poul http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-32 Mon, 11 Jun 2012 21:08:42 +0000 http://indiegamr.com/?p=72#comment-32 Note that gzip compression can only be used to send data from the server to the client, not the other way (as it has to be negotiated)

]]> By: olsn http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-30 Mon, 11 Jun 2012 05:33:48 +0000 http://indiegamr.com/?p=72#comment-30 I think you misinterpreted something here, you can pack Strings, Numbers, Hashes ect.. alike, the only difference is the output:
JSON: Object < -> String
MsgPack: Object < -> ByteArray

This means, that the OUTPUT is no String, but within your code you only work with the OBJECT anyways, that’s why it shouldn’t matter. If you are trying to generate a JSON String yourself, you probably have a design-flaw somewhere in your architecture ;-)

]]> By: Francis http://indiegamr.com/cut-your-data-exchange-traffic-by-up-to-50-with-one-line-of-code-msgpack-vs-json/#comment-29 Mon, 11 Jun 2012 03:04:25 +0000 http://indiegamr.com/?p=72#comment-29 According to https://github.com/msgpack/msgpack/issues/26 MsgPack doesn’t handle strings at all, only byte arrays.

This happens to work if you only send numbers (like coordinates and game scores), and hand-picked values (like “John Doe”), but not for user-entered data.

How many lines of code does it take to do something like JSON.stringify that works for (arbitrary) strings?

]]>