What is 8kdata? ToroDB and PostgreSQL Solutions Explained

Bridging the Relational-NoSQL Divide: The Story of 8kdata and ToroDB

In the fast-paced evolution of database technology, few challenges have been as persistent as the tug-of-war between Relational Database Management Systems (RDBMS) and NoSQL document stores. Organizations have long wrestled with a tough choice: choose the rigid structure, robust ACID compliance, and maturity of relational databases like PostgreSQL, or embrace the flexible, schema-less JSON document models of databases like MongoDB for agile application development.

Enter 8kdata, a specialized database R&D company founded in Madrid, Spain. During the height of the NoSQL boom, 8kdata proposed a compelling premise: Why reinvent the wheel for every NoSQL database when mature relational engines like PostgreSQL already master concurrency, durability, and recovery?

The Vision: Building on Giants

Founded by open-source database advocates and contributors (including key figures from the PostgreSQL community), 8kdata set out to build advanced database middleware and extensions. Rather than writing a brand-new storage engine from scratch—which often leads to immature tools lacking enterprise-grade reliability—the team leveraged PostgreSQL as a powerhouse storage and transaction layer.

Their flagship innovation was ToroDB.

What was ToroDB?

ToroDB was an open-source, MongoDB-compatible JSON document store built directly on top of PostgreSQL. It functioned as a middleware layer that allowed applications written for MongoDB to seamlessly talk to a backend powered by PostgreSQL.

Key design elements of the 8kdata approach with ToroDB included:

• The Mongo Wire Protocol (mongowp): 8kdata developed modular libraries like mongowp to interpret MongoDB wire protocol commands, allowing native driver compatibility without requiring application rewrites.
• Relational Mapping of Documents: Unlike simpler JSON wrappers that just dumped text blobs into columns, ToroDB mapped and decomposed incoming JSON documents into relational tables natively, blending document flexibility with relational querying power.
• ACID Guarantees for NoSQL Workloads: By utilizing PostgreSQL underneath, developers gained access to robust transactional consistency and reliable logging frameworks that early NoSQL systems struggled to mature.

Legacy and Industry Impact

Although 8kdata’s primary project eventually wound down its active development lifecycle cycles, the architectural philosophy championed by 8kdata proved prescient.

The strategy of combining relational engines with JSON document flexibility heavily influenced how major enterprise databases evolved. Shortly after, mainstream relational systems—most notably PostgreSQL itself with its introduction of advanced jsonb data types and indexing—adopted native document-handling capabilities, bridging the gap that 8kdata and ToroDB set out to conquer.