All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Rethinking Database Usage: When File-Based Storage Might Be Better Than Traditional Databases

By

upmostly

1mo ago· 15 min readenInsight

Summary

The article challenges conventional wisdom about database usage, arguing that databases are essentially just files on disk and that for many applications, especially early-stage ones, developers might be better off using their own file-based solutions rather than traditional databases. The author presents benchmark results comparing different storage strategies (file reading vs. in-memory loading) across three programming languages (Go, Bun, Rust) to demonstrate that simpler file-based approaches can be surprisingly performant for certain use cases.

Key quotes

· 5 pulled
A database is just files. SQLite is a single file on disk. PostgreSQL is a directory of files with a process sitting in front of them.
So the question is not whether to use files. You're always using files. The question is whether to use a database's files or your own.
And for a lot of applications, especially early-stage ones, the answer might be: your own.
Now, obviously we love databases. We're building DB Pro, a database client for Mac, Windows, and Linux.
The results are more interesting than you'd expect.
Snippet from the RSS feed
We built the same HTTP server in Go, Bun, and Rust using two storage strategies: read the file on every request, or load everything into memory. Then we ran real benchmarks. The results are more interesting than you'd expect.

You might also wanna read