Bridging Relational Power and NoSQL Flexibility: The Story of 8kdata

In the fast-evolving landscape of data management, developers have long faced a classic architectural dilemma: should they choose the rigid structure and rock-solid ACID guarantees of traditional relational database management systems (RDBMS), or lean into the agile, schema-free flexibility of NoSQL document stores?

During the mid-2010s, a database research and development company based in Spain named 8kdata stepped into this debate with a radically pragmatic answer: Why not have both?

The Genesis of 8kdata

Founded by database entrepreneur and prominent PostgreSQL community advocate Álvaro Hernández Tortosa, 8kdata was built on a bold premise. While many emerging NoSQL solutions at the time were writing new database engines entirely from scratch—often struggling for years to achieve production-grade concurrency, journaling, and data durability—8kdata recognized that a deeply mature, battle-tested engine already existed: PostgreSQL.

Instead of reinventing the wheel, 8kdata set out to build innovative layers on top of PostgreSQL, bridging the gap between relational data integrity and modern document-oriented workflows.

ToroDB: The Flagship Innovation

The crowning achievement of 8kdata’s engineering efforts was ToroDB, an open-source, MongoDB-compatible JSON document store built directly on top of PostgreSQL.

ToroDB was designed to let applications interact with it using the standard MongoDB API and wire protocol, meaning developers could drop it into existing MongoDB-backed stacks without rewriting their application queries. However, underneath the hood, the actual data management and persistence were handled securely by PostgreSQL.

Key Architectural Highlights of ToroDB:

• MongoDB Wire Protocol Compatibility: Implemented via custom libraries like mongowp, allowing seamless integration with standard MongoDB drivers and tooling.
• Relational Storage Layer: Rather than treating documents merely as flat, opaque text blobs, ToroDB took a novel approach by intelligently decomposing JSON documents and mapping them onto structured storage models within PostgreSQL.
• Inherited Enterprise Reliability: By anchoring itself to PostgreSQL, ToroDB inherited decades of community-driven optimizations, advanced transaction management, crash recovery, and data durability.

“Why all NoSQL databases are doing everything from scratch? Concurrency, durability, journaling… all those are quite tough goals to achieve. Aren’t RDBMS good enough? We think they are, especially PostgreSQL.”
— 8kdata Engineering Philosophy

Influencing the Modern Hybrid Data Era

Although 8kdata’s commercial journey eventually concluded, the conceptual footprint the company left behind remains profoundly influential.

Long before the mainstream normalization of hybrid database engines—where relational databases natively handle JSON, time-series, vector embeddings, and key-value pairs—8kdata demonstrated that traditional systems could be gracefully extended to speak multiple dialects. Their pioneering work showcased the supreme structural extensibility of PostgreSQL, anticipating a modern developer ecosystem where rigid data silos are increasingly a thing of the past.

Summary

8kdata represents a fascinating chapter in open-source database history. By cleverly marrying the API flexibility of NoSQL document stores with the uncompromised reliability of relational databases, they challenged conventional architecture and paved the way for smarter, more adaptable data infrastructure.