We all start out Jerry Seinfeld jokes with the phrase, “What’s the deal?” “What’s the deal with airline food?” He didn’t really use that phrase much, just like Andy Rooney never really said “Didya ever notice?”, but in my head when I ask the question “What’s the deal with XML?” I do it in a Jerry Seinfeld voice.

What is the deal with XML? In my last post I spoke about the reasons why XML (and JSON) are turning out to be a really big deal in the world of Big Data. Such a big deal that we

Relational databases have resulted in accidental complexity that keeps most organizations spinning in circles. Organizations simply cannot keep up with the many shapes, sizes, and types data that are quickly growing in volume and changing.

In the previous post, I discussed why today’s dynamic, constantly changing data is a problem for relational databases. In this post, I am going to discuss a somewhat related, but unique problem that is also not easy for relational databases to handle.

Today, change occurs frequently, and data modeling is a huge challenge because of the time and resources that relational databases require. Unfortunately, when using a relational database, even a simple change like adding or replacing a column in a table might be a million dollar task.

From CIOs to developers, everyone is realizing that relational databases were simply not designed for the challenges with today’s data. That’s why there’s been an explosion of data and new database products