30mb rust database client

QoreDB, an open-source desktop database client, ships as a ~30MB binary that starts in under a second, built with Tauri v2 and a native Rust backend [DevTo]. The installer weighs roughly 30MB, a fraction of the 150MB+ size typical of Electron bundles. Cold-start time measured on a 2024-generation laptop is 0.9 seconds, and idle RAM stays under 120MB, compared with DBeaver’s 800MB baseline [DevTo].

The UI is a React + TypeScript front-end rendered in the OS webview (WebView2 on Windows, WebKitGTK on Linux, WebKit on macOS). The backend runs as a single Rust binary that handles connection pooling, query execution, and streaming results over Tauri’s IPC channel. Rust’s async runtime (Tokio) streams rows in 64KB chunks, allowing the front-end to virtualize a million-row table without loading the full dataset into the DOM [DevTo].

QoreDB currently supports 15 data sources—including PostgreSQL, MySQL, MongoDB, and Redis—through a unified “resource” abstraction that maps each engine’s capabilities to a common UI. Choosing Tauri over Electron shifts maintenance burden, as the single-Chromium model of Electron guarantees identical rendering across platforms, while Tauri forces developers to handle divergent WebView quirks [DevTo].

The strict type system and ownership model of Rust eliminated data races in a multi-connection environment, a claim backed with zero incidents after months of real-world use [DevTo]. This contrasts with typical Node/Electron stacks where concurrency bugs are more common. The performance edge of Tauri + Rust comes with a hidden price: platform-specific UI bugs and slower initial development due to a fragmented driver ecosystem.