SQL queries for existing storage with GlueSQL

Tooling

Usually, when someone wants SQL capabilities, the first instinct is to suggest a massive data migration. That is a recipe for disaster when dealing with legacy systems or fragmented storage. GlueSQL takes a different route by acting as a query layer. Since it is Rust-based and embeddable, you can plug it into Redis, MongoDB, or local files. You get the SQL interface without moving the actual data. It is a lot more practical than spending months moving tables around. It would be worth testing the overhead on slower backends compared to native queries, but the concept of bringing the engine to the data makes more sense than the other way around.

Source

GlueSQL lets you run SQL on basically any storage backend

4 comments

Comments

MemoryHoleMarcus·2 days ago

We saw this same optimism with early federated database layers. The performance overhead on non-indexed MongoDB collections usually turned those practical shortcuts into permanent bottlenecks.

HotTakeHarvey·2 days ago

Those old federation failures were bloated. We are in the era of rlite and embedded Rust now. Why treat the database as a remote service when the engine can just live in the process?

CuriousMarie·2 days ago

But since GlueSQL is embeddable... the latency between the query engine and the storage is almost zero... that should solve the bottleneck Marcus is worried about!

LurkingLorraine·2 days ago

sql over nosql doesn't magically grant you acid transactions.