Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Importance of a Data Format: Part 1 — Current State Problems

DZone's Guide to

The Importance of a Data Format: Part 1 — Current State Problems

JSON is a really simple format. It's very easy to work with it, interchange it, read it, etc. However, JSON also has a few major issues. Read on to learn more.

· Database Zone
Free Resource

Traditional relational databases weren’t designed for today’s customers. Learn about the world’s first NoSQL Engagement Database purpose-built for the new era of customer experience.

JSON is a really simple format. It's very easy to work with it, interchange it, read it, etc. Here is the full JSON format definition:

object = {} | { members }
members = pair | pair , members
pair = string : value
array = [] | [ elements ]
elements = value | value , elements
value = string | number | object | array | true | false | null

So far, so good. But, JSON also has a few major issues. In particular, JSON requires you to read and parse the entire document (at least until the part you actually care about) before you can do something with it. Reading JSON documents into memory and actually working with them means loading and parsing the whole thing, and typically requires the use of dictionaries to get fast access to the data. Let us look at this typical document:

{
  "firstName": "John",
  "lastName": "Smith",
  "address": {
  "state": "NY",
  "postalCode": "10021-3100"
},
"children": [{"firstName": "Alice"}]
}

How would this look in memory after parsing?

Dictionary (root)
firstName –> John
lastName –> Smith
address –> Dictionary
state –> NY
postalCode –> 10021-3100
children –> array
[0] –> Dictionary
firstName –> Alice

So, that is three dictionaries and an array (even assuming we ignore all the strings). Using Newtonsoft.Json, the above document takes 3,840 bytes in managed memory (measured using ObjSize in WinDBG). The size of the document is 126 bytes as text. The reason for the different sizes is dictionaries. Here is 320 bytes allocation:

new Dictionary<string,Object>{ {“test”, “tube”} };

And, as you can see, this adds up fast. For a database that mostly deals with JSON data, this is a pretty important factor. Controlling memory is a very important aspect of the work of a database. And, JSON is really inefficient in this regard. For example, imagine that we want to index documents by the names of the children. That is going to force us to parse the entire document, incurring a high penalty in both CPU and memory. We need a better internal format for the data.

In my next post, I’ll go into details on this format and what constraints we are working under.

Learn how the world’s first NoSQL Engagement Database delivers unparalleled performance at any scale for customer experience innovation that never ends.

Topics:
data ,storage ,json

Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}