Other softwareAI models and assistantsLibraries and frameworksOperating systems and desktopMedia and creativeAI coding toolsInfrastructure and DevOpsTerminal and shellBrowsers and extensionsEmail and chatSelf-hosted and home serverNetworking and VPNEditors and IDEsSecurity and passwordsProductivityDatabasesFiles, sync and backupGit and code hostingNotes and knowledgeMonitoring and analyticsSearchFinance
Databases
What HN commenters recommend, ranked by distinct recommenders. Under each: what people praise most and the most common caveat, or the strongest quote where there is no summary yet.
- 1.Loved for Simplicity, Web app backends · Caveat High availability
- 2.Loved for All-in-one, Reliability at scale · Caveat Vacuum bloat
- 3.Loved for Speed, Querying files directly · Caveat Not OLTP/multi-user
- 4.Loved for Caching speed, Easy to operate · Caveat License changes
- 5.Loved for Query speed, Logging backend · Caveat Not transactional
- 6.Loved for Personal tracking, Lightweight database · Caveat Outgrown
- 7.Loved for Developer experience, All-in-one backend · Caveat RLS exposure
- 8.Loved for Redis compatibility, Trusted governance · Caveat Diverging from Redis
- 9.Loved for Offsite backups, Proven in use · Caveat Data-loss window
- 10.Loved for Simplicity, Performance · Caveat Footguns
- 11.Loved for Side projects, Productivity · Caveat Public API risk
- 12.Loved for No database ops, Branching and restores · Caveat Cost for small projects
- 13.Loved for Cloudflare integration, Low cost · Caveat Timeouts
- 14.Loved for Valued resource, Tagging and identification · Caveat User experience
- 15.Loved for No server needed, In-browser Postgres · Caveat Single connection
- 16.PgBouncer is a great piece of software. We use that heavily
- 17.I've moved from pgbouncer to pgdog a few months ago without issue. Huge fan.
- 18.Heidi has been my go-to SQL tool for longer than I can remember.
- 19.Can't recommend pgbackrest enough. It's fantastic software
- 20.Barman has always been solid for backup and restore
- 21.there's literally zero risk of the MariaDB server suddenly going closed-source
- 22.Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.
- 23.SQLite + sqlite-vec + Tantivy + a tiny embedding model will stay as my go to.
- 24.if you’re evaluating postgres, check out timescaledb.
- 25.AirTable worked somewhat to keep moving projects forward, without growing unbounded.
- 26.Moved from SQLite to libsql for native vector search.
- 27.It has worked well for me as a way to read mutable (by any client) parameters during synthesis
- 28.Then there is the DataGrip stuff, I use it all the time.
- 29.we've been using a fairly basic mssql box for years in a organisation of about 300 and it humms along nicely
- 30.I use https://github.com/ariga/atlas for this, migration based and schema base both has there good and bad side, I prefer both even in one project
- 31.I use Turso for a small project. Seems to work well.