PostgreSQL vs MySQL vs SQLite – which DB for side projects

0

Building another side project (who isn’t lol) and need to pick a database.

What I’m building: simple SaaS with users, posts, comments, basic analytics

My understanding:

  • PostgreSQL – Most powerful, bit complex
  • MySQL – Simpler, widely used
  • SQLite – For small stuff, no setup

Currently leaning towards Supabase (PostgreSQL) but plain MySQL seems easier?

0

SQLite for prototypes, PostgreSQL for production!

Dev/Prototype: SQLite. No setup, instant, perfect for side projects. Prisma/Drizzle work great with it.

Production: PostgreSQL. More robust, handles concurrency better, better data integrity.

The cool thing is: start with SQLite, switch to PostgreSQL later (Supabase/Neon). Same syntax! 👍

0

MySQL is still solid for simple projects! 👋

Been using MySQL for years. It’s battle-tested, easy to find hosting, simple to understand.

For a simple SaaS with users/posts/comments – MySQL is MORE than enough. Don’t overengineer.

That said, if you want to learn something valuable long-term, go PostgreSQL. More jobs, more features, better foundation. 🚀

0

PostgreSQL all the way. Here’s why:

PostgreSQL – Most features, best performance, JSON support, row-level security. Free and open source. Used by everyone from startups to big tech.

MySQL – Simpler but less powerful. Good for simple read-heavy apps. MariaDB is the open-source alternative.

SQLite – Great for local dev, prototypes, small apps. No server needed!

For side projects: Start with Supabase (PostgreSQL). Easy setup, generous free tier, scales with you. 🔥