What should I use instead of MySQL for a new app?

It depends on what you need, but for a new app, the most common “instead of MySQL” choices are:

1. PostgreSQL — best default for most new apps

Use this if you want a solid relational database with strong features.

• Great SQL support
• Better support for complex queries, JSON, indexing, and constraints
• Very reliable and widely used
• Often the safest choice for greenfield projects

If you’re unsure, pick PostgreSQL.

2. SQLite — best for simple apps, prototypes, or local-first apps

Use this if:

• your app is small to medium
• you want zero server setup
• you’re building mobile, desktop, embedded, or a prototype

It’s extremely easy to use, but not ideal for heavy concurrent writes or large multi-user server apps.

3. MongoDB — if your data is document-shaped and schema changes a lot

Use this if:

• your data is naturally JSON/document-based
• you want flexible schema
• relationships are not very complex

But don’t choose it just because it seems easier; many apps are better with PostgreSQL.

4. Cloud-managed relational databases

If you want less ops work, consider:

• Amazon Aurora PostgreSQL
• Google Cloud SQL
• Azure Database for PostgreSQL
• Neon / Supabase / AlloyDB

These give you PostgreSQL with easier scaling/management.

Quick recommendation

• Most web apps: PostgreSQL
• Tiny/simple app or prototype: SQLite
• Document-heavy app: MongoDB
• Want managed cloud with minimal ops: PostgreSQL on a managed platform

If you tell me:

1. app type,
2. expected traffic,
3. whether you need transactions/joins, I can recommend a specific database stack.