The Evolution of 8Kdata: Bridging Relational and NoSQL Databases with PostgreSQL

In the dynamic world of database technology, few architectures have proven as versatile or enduring as PostgreSQL. Over the years, specialized research and development firms have sought to push its boundaries, adding entirely new dimensions to its capabilities. Among them, 8Kdata—a database R&D company founded in Spain by veteran technologist Álvaro Hernández Tortosa—left a distinct mark on the open-source ecosystem by reimagining how relational systems handle unstructured and semi-structured data.

The Vision Behind 8Kdata

Founded with a core focus on advanced database engineering, 8Kdata emerged to tackle one of the most prominent friction points in modern application development: the historical divide between relational databases (SQL) and document stores (NoSQL).

While relational engines like PostgreSQL offered unmatched transactional safety, consistency, and standard query power, the rise of web-scale applications heavily favored the schema-less, JSON-friendly flexibility of databases like MongoDB. Rather than forcing developers to choose between these two distinct paradigms, 8Kdata set out to bridge the gap at the architectural level.

ToroDB: The Flagship Innovation

The crowning achievement of 8Kdata’s engineering efforts was ToroDB, an open-source, document-oriented JSON database built directly on top of PostgreSQL.

ToroDB effectively transformed PostgreSQL into a fully functional NoSQL document database. Key aspects of its architecture included:

• MongoDB Compatibility: ToroDB was designed to be compatible with MongoDB clients and protocols, allowing it to function either as a standalone database or even as a secondary node within a MongoDB replica set.
• Relational Backbone: Beneath the document-centric interface, it leveraged PostgreSQL’s robust storage engine, transactional guarantees (ACID compliance), and powerful tooling.
• Complex Queries: It aimed to resolve performance bottlenecks and query complexity issues (such as aggregate analytics) that traditional document stores occasionally encountered, utilizing PostgreSQL’s mature query planner.

Technical Highlights at a Glance

| Feature / Aspect | Description |
| :— | :— |
| Primary Project | ToroDB (Open-source under AGPLv3) |
| Core Technology | PostgreSQL-backed document integration layer |
| Primary Use Case | Running NoSQL document workloads natively on a relational engine |
| Ecosystem Role | Pioneering hybrid paradigms bridging SQL reliability and NoSQL flexibility |

Legacy and Impact

Although the database landscape continues to evolve—with newer projects and extensions continuously redefining what PostgreSQL can achieve—8Kdata’s pioneering work laid critical groundwork for modern multi-model database concepts. By proving that a relational powerhouse like PostgreSQL could be cleanly adapted to handle document-centric workflows without sacrificing its core strengths, 8Kdata helped expand the horizons of database architecture.

Today, the spirit of expanding PostgreSQL into hybrid workloads lives on through ongoing innovations in the global open-source community, making 8Kdata a fascinating chapter in the history of modern database engineering.