2 ms·
Json doesn't support polymorphism and circular/shared references, those scenarios are more suitable for fury. And json is a text protocol, which is inefficient
by chaokunyang 3y ago
Json doesn't support polymorphism and circular/shared references, those scenarios are more suitable for fury. And json is a text protocol, which is inefficient compared to fury binary protocol. Taking jackson json lib as an example:
1) Fury is 41.6x faster than jackson for Struct serialization
2) Fury is 65.6x faster than jackson for Struct deserialization
3) Fury is 9.4x faster than jackson for MediaContent serialization
4) Fury is 9.6x faster than jackson for MediaContent deserialization
For http rest api, json is more suitable. For RPC/bigdata/game/scheduling, fury may be better
- gigatexal 3y agoThank you chao!
- chaokunyang 3y agoAnother issue for json format is that it will bloat the payload. For example, for an int `1111122222` will take 10 bytes in json, but only 4 bytes in fury. `0.3333333333333333` will need 18 bytes in json, but only 4 bytes in fury.