When you hear “Sony,” you may conjure images of televisions, PlayStations®, TV shows like Breaking Bad or even the little robot dog. It’s a mind-bogglingly large $77 billion business, and at MarkLogic World this year, Sony’s Vice President of IT Rob Maxwell gave us a glimpse into one portion of the business’s complexity: Sony Pictures Television.

Rob was onstage with MarkLogic’s EVP of Products, Joe Pasqua, discussing Sony’s challenging yet common aging IT infrastructure and

Few industries have greater access to data to drive analytics and insights than the retail industry. Data is the heart of this business. Yet as retailers prepare for another busy holiday season they face four significant data challenges that will help distinguish between the winners from the losers.

1. Bridging the data gaps between in-store and online
   
   Consumers expect consistent treatment and a seamless experience from retailers regardless of the channel they use– be it in-store, online, via

The pace of change today means that companies and technologies will rise and fall faster than ever, and “innovate or die,” has never been more accurate.

As the Oracle OpenWorld conference winds down, not much was said about next-generation database technology – in particular Enterprise NoSQL databases. It’s the next-generation database technology that MarkLogic has made so enterprise-hardened that well over 50 percent of our business is a result of finishing projects that customers started

Relational databases require ORM, which extracts the data away, tearing apart the data and adding more overhead in the process.

This post is the last one in my series about “why RDBMS aren’t working” to handle today’s data challenges. The previous posts focused on the relational data model being a poor fit for today’s data, and in this post I’m going show why the relational data model is a poor fit for modern app development.

Today, it’s a

Relational databases are designed for either OLTP or OLAP workloads. You can’t use one database for both. Today, that limitation is no longer acceptable as IT struggles to keep pace with the speed of business.

To recap, in previous posts I discussed two aspects of how relational databases have inflexible data models that are not designed for change, are not designed to handle data variety, and are not designed for scale. In this post, I am going to discuss another problem that has