Haven't used DBlicious yet?
Ask Trustburn

Questions about DBlicious

Based on 5 reviews, listing data and website checks · updated 4 days ago

What is DBlicious?

DBlicious is an open-source engineering preview that adapts PostgreSQL and MySQL to use external, immutable S3-compatible object storage for durable logs and page history. It separates compute engines from the storage layer using Rust-based infrastructure to provide fenced write quorums and remote page layers. The project currently lists a working PostgreSQL 18 prototype and verified MySQL 8.4 LTS acceptance, supporting native clients without translating SQL or requiring proprietary drivers.

How do the four clean layers of DBlicious work together?

The system operates with four clean layers: connecting native psql or mysql clients to upstream compute, managing commit WAL or redo durability via a 2-of-3 keeper quorum, materializing page services with sparse writable overlays, and retaining S3-compatible history on backends like Cloudflare R2, MinIO, or AWS S3.

What specific durability mechanisms does DBlicious use for PostgreSQL and MySQL?

PostgreSQL 18 commits cross a fenced log quorum, while MySQL flushes across a 2-of-3 fsync keeper quorum and immutable S3-compatible redo storage before acknowledgement. Both engines gate durable acknowledgement on this fenced quorum to ensure data integrity before completion.

How does the materialized page service layer handle page operations?

The architecture includes separate PostgreSQL and InnoDB page adapters that utilize sparse writable overlays and bounded reconstruction. These materialized page services allow the system to handle page-level operations efficiently without duplicating history.

What techniques are used to retain immutable history and support branching?

Immutable snapshots, bounded log-manifest deltas, incremental overlays, and O(1) branching are used to retain S3-compatible history. These features allow the system to reuse history instead of duplicating it for branches.

Which native clients and tools are supported for PostgreSQL and MySQL?

The system supports native PostgreSQL 18 clients such as psql, libpq, JDBC, psycopg, pgx, and ordinary PostgreSQL tooling. For MySQL 8.4 LTS, it connects with the mysql CLI, Connector/J, Go, Python, Node.js, PHP, and ordinary MySQL libraries.

What specific verification scenarios have been tested for MySQL on MinIO?

The system verifies immutable InnoDB layers and redo-before-ACK on MinIO, including one-keeper-loss commit paths and lagging-keeper catch-up scenarios. It also handles fresh-PVC recovery from immutable snapshots plus archived redo.

How does the system manage remote page eviction and cache refresh?

The architecture includes remote page eviction, refill, compaction, and cache refresh mechanisms. These features manage the lifecycle of pages stored in the immutable layers and object storage.

How does DBlicious handle Cloud SQL 8.0 database cloning and compatibility?

The system supports Cloud SQL 8.0 database cloning into patched upstream MySQL 8.4, allowing unmodified PHP applications and native clients to live alongside the changes. This ensures compatibility with existing workflows.

What are the terms for accessing the DBlicious preview?

The system provides a free preview with provisioning disabled for the engineering preview phase. This allows users to explore the design and actual database engines without immediate provisioning.

What is the official website of DBlicious?

The official website of DBlicious is dblicio.us.

How is DBlicious rated on Trustburn?

On Trustburn, DBlicious has a rating of 4.4 out of 5 based on 5 reviews.

Based on reviews, listing data and the company's website. Verify anything important with the company directly.

David Chen
Reviews 1

This is a genuinely exciting development for the database world. DBlicious is effectively unbundling PostgreSQL and MySQL while keeping their native SQL semantics intact. The infrastructure is built on Rust, which promises excellent performance. I am particularly impressed by the verified recovery drills and the use of S3-compatible storage for immutable page history. The ability to branch and scale without copying the entire database is a game-changer for efficiency. The engineering preview shows real application traffic passing acceptance tests. Having the compute boundary separate from the storage plane allows for much more flexible scaling. The team has clearly prioritized durability and recovery, as evidenced by the 2-of-3 quorum mechanisms. This approach feels like the future of database management.

Maria Gonzalez
Reviews 1

Connectivity via standard psql, mysql CLI, and ordinary language drivers makes integration seamless for existing workflows without requiring new proprietary tools.

Julian Thorne
Reviews 1

The verified recovery times are genuinely impressive. PostgreSQL demonstrated arbitrary-LSN replay, and MySQL restored a real Cloud SQL database while serving an unmodified PHP application. The ability to recover from immutable history on MinIO and resume blocked commits after a majority outage shows robust engineering. It is a refreshing approach compared to traditional monolithic databases.

Elena Vasquez
Reviews 1

From the information available, DBlicious presents an interesting architecture that separates compute from storage for both PostgreSQL and MySQL. The emphasis on durable engine logs and immutable page history stored on R2, MinIO, or S3 suggests a focus on data integrity and recoverability. The use of a fenced 2-of-3 keeper quorum for acknowledgments is a notable detail that implies strong consistency guarantees. However, since this is described as an active engineering preview and not a production database offer, the service offering seems promising but not yet fully mature. Customer provisioning is currently waiting for further recovery, compatibility, and performance evidence to be established. The site notes that it goes live early, which means the available features are still being validated. While the separation of upstream SQL semantics from the storage layer is architecturally sound, the practical implications for existing applications remain to be seen. One must consider that the current status indicates a constrained beta canary is the next milestone, rather than an automatic production cutover. Therefore, while the technical foundation appears solid, the overall product experience is still evolving and requires careful evaluation before full adoption.

Arthur Pendelton
Reviews 1

The engineering preview for DBlicious presents a compelling unbundled database architecture. Combining PostgreSQL and MySQL with durable engine logs on S3-compatible storage offers significant flexibility. The use of Rust for infrastructure and native clients ensures high performance without proprietary driver overhead. Verified recovery drills and immutable page layers demonstrate a mature approach to data durability. This professional implementation of upstream compute with shared storage and control plane infrastructure is exactly what modern distributed systems require for scalable, reliable database operations.

Questions & Answers

No questions yet — be the first to ask.

News & Press

No news yet. This is where the business shares its own updates and press.

Photos

No photos yet. Photos shared by reviewers will show up here.

Widgets

Boost your business trust by displaying widget on your website — its a simple way to convert your visitors into customers.

Embed code

<script src="https://trustburn.com/widgets/index.js"></script>
<div class="trustburn-widget" data-trustburn-protocol="https:" data-trustburn-domain="trustburn.com" data-trustburn-widget="score" data-company-path="dblicio-us" data-lang="en"></div>
More widgets

About DBlicious

DBlicious is a software project that adapts PostgreSQL and MySQL database engines to use external, immutable, S3-compatible object storage for durable logs and page history. It separates the upstream compute engines from the storage layer, using Rust-based infrastructure to provide fenced write quorums, remote page layers, branching, and recovery without copying the entire database. The product supports native PostgreSQL and MySQL clients and tooling without translating SQL or requiring proprietary drivers. It currently lists a working PostgreSQL 18 prototype and verified MySQL 8.4 LTS acceptance, and the site indicates the project is an open-source engineering preview still in active development.

Website
dblicio.us