Big Data/Analytics Zone is brought to you in partnership with:

John Cook is an applied mathematician working in Houston, Texas. His career has been a blend of research, software development, consulting, and management. John is a DZone MVB and is not an employee of DZone and has posted 168 posts at DZone. You can read more from them at their website. View Full User Profile

The Big Data Cube

10.10.2012
| 4268 views |
  • submit to reddit

Erik Meijer’s paper Your Mouse is a Database has an interesting illustration of “The Big Data Cube” using three axes to classify databases.

The volume axis is big vs. small, or perhaps better, open vs. closed. Relational databases can be large, and non-relational databases can be small. But the relational database model is closed in the sense that “it assumes a closed world that is under full control by the database.”

The velocity axis is (synchronous) pull vs. (asynchronous) push. The variety axis captures whether data is stored by foreign-key/primary-key relations or key-value pairs. The first axis could be labeled

Here are the corners identified by the paper:

  • Traditional RDBMS (small, pull, fk/pk)
  • Hadoop HBase (big, pull, fk/pk)
  • Object/relational mappers (small, pull, k/v)
  • LINQ to Objects (big, pull, k/v)
  • Reactive Extensions (big, push, k/v)

How would you fill in the three corners not listed above?

Published at DZone with permission of John Cook, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)