MarkLogic

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

Research organization TDWI recently published an online survey and assessment guide to help organizations determine how ready they are to adopt and implement Hadoop. In the past few years, the number of organizations using Hadoop—or contemplating using it—has grown astronomically. Each organization has common questions about whether they are really ready to implement Hadoop, and […]

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