# Benefits of "MySQL-backed installs"?

**URL:** <https://discuss.write.as/t/benefits-of-mysql-backed-installs/19733>\
**Category:** Installation\
**Tags:** writefreely\
**Created:** [October 4, 2025, 1:26am UTC](https://discuss.write.as/t/benefits-of-mysql-backed-installs/19733 "2025-10-04T01:26:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bouncinglime](https://discuss.write.as/user_avatar/discuss.write.as/bouncinglime/32/5435_2.png) [@bouncinglime](https://discuss.write.as/u/bouncinglime)\
**Post date:** [October 4, 2025, 1:26am UTC](https://discuss.write.as/t/benefits-of-mysql-backed-installs/19733/1 "2025-10-04T01:26:13Z")

</div>

I’m looking at installing WriteFreely, and am curious about what the benefits are of a “MySQL-backed install”. That aspect of WF is mentioned only on the install page, and I’m not seeing anything about it here other than folks having issues with MySQL.

What’s the difference? What do I get with it / why should I use it? What do I get without it / why should I not use it?

---

<div class="post-metadata">

**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\
**Post date:** [October 6, 2025, 5:02pm UTC](https://discuss.write.as/t/benefits-of-mysql-backed-installs/19733/2 "2025-10-06T17:02:33Z")

</div>

The main reason to use MySQL would probably be that you already have a MySQL server running, or just prefer to work with that. You might also plan to run multiple WriteFreely application servers, e.g. behind a load balancer, and having a single MySQL database behind them can simplify this setup – though I haven’t heard of anyone doing this (outside of our large instance on Write.as).

Otherwise, SQLite is great for simplified installations, as everything is stored in a single SQLite file on the local machine. Ultimately, it’s really up to your individual preference.

---

<div class="post-metadata">

**Author:** ![bouncinglime](https://discuss.write.as/user_avatar/discuss.write.as/bouncinglime/32/5435_2.png) [@bouncinglime](https://discuss.write.as/u/bouncinglime)\
**Post date:** [December 23, 2025, 5:43am UTC](https://discuss.write.as/t/benefits-of-mysql-backed-installs/19733/3 "2025-12-23T05:43:56Z")

</div>

Thanks for the info! It was unclear if any sort of SQL was required for a WriteFreely.

---

<div class="post-metadata">

**Author:** ![Carole123](https://discuss.write.as/letter_avatar_proxy/v4/letter/c/3d9bf3/32.png) [@Carole123](https://discuss.write.as/u/Carole123)\
**Post date:** [December 31, 2025, 5:34pm UTC](https://discuss.write.as/t/benefits-of-mysql-backed-installs/19733/4 "2025-12-31T17:34:30Z")

</div>

The MySQL-backed route on WriteFreely is only important if you need more than one app instance to share a data store or if you’re already deep in MySQL land. SQLite is usually easier and just works for single-node setups. There are no extra parts that need to move. I only use MySQL when I need to scale or when I need to use other tools with the database.