An Introduction to 8kdata and Its PostgreSQL Tools

Bridging Worlds: The Story of 8kdata and its PostgreSQL Revolution

In the dynamic landscape of enterprise software and database architecture, few projects challenge the status quo quite like those born from 8kdata. As a specialized database research and development firm rooted in Spain, 8kdata carved out a unique niche by refusing to choose sides in the classic ideological divide between relational (SQL) and non-relational (NoSQL) databases.

Instead, they leveraged the rock-solid reliability of open-source technology to build bridges, creating tools that redefined how developers think about data storage, protocol compatibility, and database extensibility.

The Genesis: Rethinking NoSQL on a Relational Core

Founded by database veterans—including prominent figures in the PostgreSQL community like Álvaro Hernández Tortosa—8kdata set out to solve a fundamental friction point for modern engineering teams.

For years, organizations building web-scale applications faced a difficult compromise:

• The NoSQL Promise: Loved for its flexible JSON document structures and developer-friendly syntax (typified by MongoDB), but historically lacking the bulletproof ACID compliance and transactional safety of mature relational engines.
• The Relational Standard: Celebrated for data integrity, ACID guarantees, and advanced querying power (typified by PostgreSQL), but traditionally requiring rigid schemas that could slow down rapid application iteration.

Rather than building a NoSQL database from scratch—an endeavor fraught with peril regarding concurrency, durability, and journaling—8kdata asked a provocative question: “Aren’t relational databases good enough? Specifically, isn’t PostgreSQL powerful enough?”

ToroDB: The Flagship Innovation

The answer to that question materialized as ToroDB, 8kdata’s most notable contribution to the open-source ecosystem. ToroDB was a document-oriented, MongoDB-compatible database built entirely on top of PostgreSQL.

Unlike other JSON-handling layers that simply treated documents as blobs, ToroDB took a novel approach. It allowed applications to speak the MongoDB wire protocol and query language natively while mapping and storing the data relationally inside PostgreSQL.

Key architectural wins of ToroDB included:

• Seamless Compatibility: Developers could use existing MongoDB drivers and tools without rewriting application layers.
• Relational Back-End Strength: Data gained the transactional safety, reliability, and concurrency features inherent to PostgreSQL.
• Flexible Deployment: It could operate either as a standalone database or function directly as a secondary node inside a MongoDB replica set.

Beyond ToroDB: Engineering Contributions

8kdata was much more than a single-product startup; it operated as an advanced database R&D lab. The team contributed heavily to the broader database ecosystem through open-source tooling, performance measurement frameworks, and asynchronous driver toolkits (such as phoebe for building asynchronous PostgreSQL drivers).

Their engineering ethos centered around transparency, community leadership (such as heavily driving the Spanish PostgreSQL Association), and rigorous benchmarking—such as quantifying the exact micro-level network and driver overheads of running complex workloads across different programming environments.

Legacy and Modern Context

The core philosophy championed by 8kdata—that PostgreSQL is infinitely extensible and capable of absorbing alternative paradigms like document storage, vector search, and time-series analytics—has heavily influenced modern database design.

As enterprises increasingly demand unified data architectures that can handle structured transactions and flexible document models simultaneously without proliferating separate data silos, the pioneering work of 8kdata looks remarkably ahead of its time. By proving that you don’t need to reinvent the wheel to innovate, 8kdata left an enduring footprint on the evolution of open-source data infrastructure.