# What are the shortcomings of running Temporal with SQLite in production (for small-scale use cases)?

**URL:** <https://community.temporal.io/t/what-are-the-shortcomings-of-running-temporal-with-sqlite-in-production-for-small-scale-use-cases/18257>\
**Category:** Developer Corner\
**Tags:** go-sdk\
**Created:** [August 22, 2025, 6:11pm UTC](https://community.temporal.io/t/what-are-the-shortcomings-of-running-temporal-with-sqlite-in-production-for-small-scale-use-cases/18257 "2025-08-22T18:11:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![omid\_gholami](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/omid_gholami/32/5857_2.png) [@omid\_gholami](https://community.temporal.io/u/omid_gholami)\
**Post date:** [August 22, 2025, 6:11pm UTC](https://community.temporal.io/t/what-are-the-shortcomings-of-running-temporal-with-sqlite-in-production-for-small-scale-use-cases/18257/1 "2025-08-22T18:11:40Z")

</div>

Hey,  
I’ve noticed in the Temporal docs that SQLite v3.x persistence is supported, but only for development and testing, _not_ for production. I understand that PostgreSQL and MySQL are the officially supported production backends, but I’m curious to understand more deeply _why_ SQLite is discouraged (even for small to medium use cases?)

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [August 22, 2025, 6:12pm UTC](https://community.temporal.io/t/what-are-the-shortcomings-of-running-temporal-with-sqlite-in-production-for-small-scale-use-cases/18257/2 "2025-08-22T18:12:54Z")

</div>

SQLite can be used from a single process only. Temporal service is scaled out by adding processes that share a single DB.