Running Frappe v15 on Amazon Aurora MySQL — Is it viable? Has anyone done it?

Frappe Framework
, ,
1

Running Frappe v15 on Amazon Aurora MySQL — Is it viable? Has anyone done it?

Background:
Our company is fully on AWS and is required to use Amazon Aurora (MySQL-compatible). We have multiple existing Frappe-based projects — including an ERP system — that we’ve been running for 2–3 years and need to understand if migrating them to Aurora is feasible, or if we should avoid it entirely.

We are on Frappe v15 and are not planning to upgrade to v16. We are open to applying manual patches where needed, but we want to understand the scope before committing to this.

I already read this thread before posting:
:backhand_index_pointing_right: Support for MySQL 8.0 and MySQL enterprise edition

Particularly @revant_one’s note about running ERPNext on Aurora with manual sed patches on v13. We want to know if anything equivalent exists or is needed for v15.

What we found in the codebase

Looking at frappe/database/utils.py and frappe/database/__init__.py — the DB routing only handles mariadb, postgres, and sqlite. There is no MySQL branch anywhere at the routing level.

Additionally, frappe/database/mariadb/schema.py uses:

  • CREATE SEQUENCE — not supported in MySQL/Aurora
  • Native uuid column type — not supported in MySQL/Aurora

These are hard blockers at the schema layer, not just config-level issues.

The migration question

Our company wants to consolidate all databases onto AWS Aurora MySQL. We have:

  • 2–3 years of Frappe-based projects in production
  • An ERPNext installation
  • Several custom Frappe apps

We are considering two paths:

  1. Patch Frappe v15 to work with Aurora MySQL — apply and maintain patches ourselves, similar to what @revant_one described for v13
  2. Migrate to Django — rewrite the platform on a framework with proper MySQL support

We lean toward option 1 for now, since a Django rewrite would be a very large undertaking given the scope of existing Frappe customizations, DocTypes, hooks, and ERPNext modules already in production. That said, we want to understand if the patching approach is sustainable long-term.

Specific questions

  1. Has anyone successfully run Frappe v15 on Aurora MySQL — with or without patches?
  2. Are the v13-era patches still structurally valid, or has the DB layer changed enough in v14/v15 that a different approach is needed?
  3. Is there a maintained fork, wrapper, or compatibility layer for Frappe + MySQL that we should know about?
  4. For teams in a similar position — stay and patch, or is “don’t do it, here’s why” the honest answer?

Any experience, pointers, or contacts from people who’ve navigated this would be very helpful. Even a clear “this is a dead end” is useful at this stage.

Thanks in advance :folded_hands:

2

@ankush @rmehta @buildwithhussain
any thoughts?