# Give each of your users their own SQLite database

DevFeed: [Give each of your users their own SQLite database](<https://devfeed.tech/articles/give-each-of-your-users-their-own-sqlite-database-5953.md>)

Original publisher: [Read original article](<https://turso.tech/blog/give-each-of-your-users-their-own-sqlite-database-b74445f4>)

Author: Jamie Barton

Published: 2024-01-26T00:00:00Z

Content type: tutorial

Language: en

Sources: [Turso Blog](<https://devfeed.tech/sources/turso-blog.md>)

Topics: [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [database](<https://devfeed.tech/tags/database.md>), [migration](<https://devfeed.tech/tags/migration.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [per-user-database](<https://devfeed.tech/tags/per-user-database.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

## AI overview

The article describes migrating an application from a shared multi-tenant database to a separate SQLite database for each user. It considers simpler data isolation and queries, while raising schema migration and cross-user reporting concerns.

## Source excerpt

Journey from multi-tenant to SQLite single-tenant architecture, inspired by DHH's vision. One user, one database.