Azure stopping support for MariaDB — Is using PostgreSQL or MySQL for Frappe production advisable?

Frappe Framework
, ,
1

Hello Frappe community,

I am planning to deploy a Frappe/ERPNext site on Azure, but I noticed that Azure has stopped offering managed MariaDB.

I am considering using either PostgreSQL or MySQL as the database backend.

My questions are:

  1. Is it safe and recommended to use MySQL for a production Frappe site?
  2. Can PostgreSQL be used reliably in production, or will it cause login/authentication or feature issues?
  3. Are there any known limitations or pitfalls when running Frappe on these databases instead of MariaDB?
  4. If PostgreSQL is not advisable, what is the best approach to deploy Frappe on Azure given the lack of MariaDB support?

Any guidance, experiences, or best practices would be highly appreciated.

Thank you!

2

Hey, good question! From what I know, MySQL and MariaDB share almost the same configuration and syntax, so if Azure has dropped managed MariaDB, MySQL is a pretty safe swap. You shouldn’t run into major issues there — most Frappe setups that work on MariaDB translate cleanly to MySQL without much friction.

PostgreSQL is a different story though, Frappe’s support for it has historically been incomplete so I’d avoid it for production unless things have changed recently.

One thing I’ll mention — I haven’t personally worked with Azure deployments, I’ve used other platforms, so I can’t speak to the Azure-specific part of your question. But if MySQL is available as a managed option there, that’d be my first thing to check before going down any other route.

Hope that helps, someone with Azure experience can probably fill in the gaps!

1 Like