> For the complete documentation index, see [llms.txt](https://functional.gitbook.io/database_comparison_report/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://functional.gitbook.io/database_comparison_report/mysql/cons-of-mysql.md).

# Cons of MySQL

**Scalability challenges.** MySQL was not built with scalability in mind, which is inherent in its code. In theory, you can scale MySQL, but it will need more engineering effort as compared to any of the NoSQL databases. So, if you expect one day your database will increase substantially, keep this limitation in mind or choose another DBMS option.

**Partial open-source support.** Although MySQL has the open-source part, it’s mostly under Oracle’s license. This limits the MySQL community in terms of improving the DBMS. Why do you care? Because when you have completely open-source support, you expect many problem-specific implementations and community assistance. This is not the case when the software belongs to corporate owners and you’ll have to pay for support.

**Limited compliance with SQL standards.** Structured Query Language has specific standards. MySQL doesn’t completely follow them, i.e. MySQL provides no support for some standard SQL features. On the other hand, MySQL has some extensions and distinct features that don’t match the Structured Query Language standards. It’s not a big deal for small web applications. The issues may appear when you have to shift to other databases, which is likely to happen when your business starts growing.