Click here to Skip to main content
Click here to Skip to main content


, 26 Mar 2012 CPOL
Rate this:
Please Sign up or sign in to vote.
A binary JSON serializer based on fastJSON
This is an old version of the currently published article.


The code is now on CodePlex under Git source control (


fastBinaryJSON is based on my fastJSON article ( and code which is a polymorphic object serializer. The main purpose for fastBinaryJSON is speed in serializing and deserializing data for the use in data transfer and storage to disk. It was created for my upcoming RaptorDB -  Document Database engine, for performance.


fastBinaryJSON has the following feature list: 

  • Based on fastJSON code base (very fast, polymorphic)
    • Supports : HashTables, Dictionary, Generic Lists, Datasets, ...
  • Typically 2-10% faster on serialize, 17%+ faster on deserialize. 


Why another serializer you may ask, why not just use fastJSON? The answer to this is simple : performance. JSON while a great format has the following problem:

  • JSON is a text format, so you loose type information on serializing which makes deserializing the data again time consuming. 

Why not BSON?

Why not just use BSON ( you may ask? The answer is the following:

  • Looking at the specifications on the above site, you feel overwhelmed as it is hard to follow.
  • You feel that the specs have evolved over time and a lot of the coding parts have been deprecated.
  • BSON encodes lengths into the stream which inflate the data, this might be fine for the use case the authors envisioned, but for data transfer and storage it just makes things larger than they need to be.
  • Because of the length prefixes, the encoding of the data object must be done in two passes, once to output the data, and a second time to set the length prefixes.

I initially started off by doing a BSON conversion on fastJSON but it got too complicated, so it was scrapped.  

How is data encoded in fastBinaryJSON?  

JSON is an extremely simple format, so fastBinaryJSON takes that simplicity and add the needed parts to do binary serialization. fastBinaryJSON follows the same rules as the JSON specification ( with the following table showing how data is encoded: 

As you can see  from the above all the encoding rules are the same as JSON and primitive data types have been given 1 byte tokens for encoding data. So the general format is :

TOKEN,  { DATA } : where DATA can be 0 or more bytes

Strings can be encoded in 2 ways, as UTF8 or Unicode, where UTF8 is more space efficient and Unicode is faster.

String keys or property names are encoded as a special UTF8 stream which is limited to 255 bytes in length to save space (you should not have a problem with this as most property names are short in length).

Performance tests

To get a sense of the performance differences in fastBinaryJSON against fastJSON the following tests were performed, times are in milliseconds, each test was done on 1000 objects and repeated 5 times, the AVG column is the average of the test excluding the first which is skewed by initialization times:

As you can see in the DIFF column which is [ fastJSON / fastBinaryJSON ] the serializer performs at least 2% faster  and the deserializer at least 17% faster, with the greatest difference being with DataSet types which are a lot of rows of data.

Using the code 

To use fastBinaryJSON you can use the following code samples:

byte[] bytes = fastBinaryJSON.BJSON.Instance.ToJSON(obj);
byte[] bytes = fastBinaryJSON.BJSON.Instance.ToJSON(obj, true, true); // optimized dataset, unicode strings

object obj = fastBinaryJSON.BJSON.Instance.ToObject(bytes);
SalesInvoice obj = fastBinaryJSON.BJSON.Instance.ToObject<SalesInvoice>(bytes); // type is known 

There are 3 parameters which control how the serialization is done which can be set on the Instance or can be done by a per call basis like the above examples :

UseOptimizedDatasetSchemaUse an optimized format to serialze the Dataset Schema (default = True)
ShowReadOnlyPropertiesSerialize ReadOnly Properties (default = False)
UseUnicodeStringsUse Unicode encoding for strings (default = True)


  • Initial Release : 25th March 2012
  • Update : 26th March 2012
    • Added link to codeplex source control


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Mehdi Gholam
United Kingdom United Kingdom
Mehdi first started programming when he was 8 on BBC+128k machine in 6512 processor language, after various hardware and software changes he eventually came across .net and c# which he has been using since v1.0.
He is formally educated as a system analyst Industrial engineer, but his programming passion continues.
* Mehdi is the 5th person to get 6 out of 7 Platinums on CodeProject (13th Jan'12)

Comments and Discussions

Discussions posted for the Published version of this article. Posting a message here will take you to the publicly available article in order to continue your conversation in public.
Questionmention of your work on Scott Hanselman's blog PinmemberBillWoodruff11-Aug-12 7:30 
AnswerRe: mention of your work on Scott Hanselman's blog PinmvpMehdi Gholam11-Aug-12 8:26 
AnswerRe: mention of your work on Scott Hanselman's blog [modified] Pinmembercycnus11-Aug-12 18:02 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.150327.1 | Last Updated 26 Mar 2012
Article Copyright 2012 by Mehdi Gholam
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid