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

The Big Data Cube

DZone's Guide to

The Big Data Cube

· Big Data Zone ·
Free Resource

Learn how to operationalize machine learning and data science projects to monetize your AI initiatives. Download the Gartner report now.

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?

Bias comes in a variety of forms, all of them potentially damaging to the efficacy of your ML algorithm. Our Chief Data Scientist discusses the source of most headlines about AI failures here.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}