Understanding 8kdata: Database Solutions and Technology Overview

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

In the fast-paced ecosystem of database engineering, developers have long faced a classic dichotomy: should they choose the rigid structure and ACID guarantees of relational databases (RDBMS), or the agile, schema-less flexibility of NoSQL document stores?

Back in the mid-2010s, a Madrid-based database research and development startup named 8kdata stepped up to solve this exact dilemma. Though its active lifespan was relatively brief, 8kdata left an indelible footprint on modern database architecture, pioneering concepts that continue to influence how engineers bridge the gap between relational storage and document-oriented APIs.

The Vision: Why Build on PostgreSQL?

Founded by database experts and open-source enthusiasts (including key figures from the Spanish PostgreSQL community), 8kdata set out to explore new frontiers in data management. Rather than building a brand-new database from scratch—which requires reinventing the wheel regarding concurrency, crash recovery, journaling, and durability—the team decided to leverage one of the most reliable relational engines in existence: PostgreSQL.

Building storage engines from the ground up is notoriously difficult. 8kdata’s thesis was simple yet radical: PostgreSQL is good enough to handle the heavy lifting. Instead of competing with relational databases, they chose to harness Postgres’s bulletproof core while giving developers the modern API experience they craved.

ToroDB: The Flagship Innovation

8kdata’s most prominent contribution to the open-source community was ToroDB.

ToroDB was designed as an open-source, document-oriented JSON database and middleware layer that ran natively on top of PostgreSQL. Key architectural highlights included:

• MongoDB Protocol Compatibility: ToroDB spoke the Mongo Wire Protocol (mongowp), allowing applications built for MongoDB to interact seamlessly with the database layer without rewriting their query logic.
• Relational Storage Decomposition: Unlike some systems that merely shove JSON blobs into a single text column, ToroDB took incoming JSON documents and intelligently mapped them into structured relational tables behind the scenes. This allowed users to query unstructured data using powerful SQL tools while maintaining a NoSQL developer experience.
• The Best of Both Worlds: It aimed to marry the high concurrency, indexing power, and durability of PostgreSQL with the agile, flexible schema design of document databases.

Legacy and Modern Parallels

Although 8kdata eventually wound down its operations and ToroDB became an archived project by the late 2010s, the technical problem 8kdata tried to solve has only grown more relevant.