MarkLogic

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 […]

Relational databases are designed to run on a single server in order to maintain the integrity of the table mappings and avoid the problems of distributed computing. We’re at a tipping point with data volume. In my last post, I showed the stat from EMC about how the digital universe is expected to grow from […]

Delivering on the promise of personalization calls for a 360-degree view of your consumers, products and in-store data. Personalization seems to have replaced omnichannel as retailing’s hottest buzzword! At the Conext Connected Commerce Show, held last month in Lille, France, it seemed like every Retail exhibitor felt that personalization needed to be part of its message. […]

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 […]