Choosing a solo-project database: include deployment and language tooling
After moving from familiar MongoDB to Postgres, a developer values deployment behavior and integration with Rust tooling.
The takeaway
Evaluate everyday development and deployment, not just data structures.
The context
The commenter initially stayed with MongoDB because it was what they learned. For a translation-cache project, they used Postgres and reported fewer deployment issues and a good fit with SQLx. They also suggest normalizing awkward incoming data. This is a project-and-toolchain fit story, not a universal database ranking.
Steps worth trying
Editorial suggestions, not promises made by the original author.
- 01
Test real queries and deployment targets, including drivers, migrations, and backup recovery.
- 02
Give incoming-data normalization an explicit boundary and track query complexity caused by retaining awkward formats.
Where this applies — and where it may not
This is one developer’s historical experience with limited workload details and no controlled performance comparison.
From the discussion
“Rust's SQLx library works really well.”
@Alex-Programs · View source
Favorite general purpose database for solo proejcts?
@thenooby · 2 points · 10 comments
Read the Hacker News threadSource: OpenIndex Hacker News dataset (ODC-By). Original content belongs to its authors. Summaries, translations, and suggested steps are AI-assisted editorial work. Read the sources; individual outcomes are not guarantees.