<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sqlite on iSquiz.com</title><link>https://www.isquiz.com/tags/sqlite/</link><description>Recent content in Sqlite on iSquiz.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>iSquiz.com</copyright><lastBuildDate>Sat, 15 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.isquiz.com/tags/sqlite/index.xml" rel="self" type="application/rss+xml"/><item><title>When to Move From SQLite to Postgres for a Growing App</title><link>https://www.isquiz.com/post/sqlite-to-postgres-growing-app/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.isquiz.com/post/sqlite-to-postgres-growing-app/</guid><description>
&lt;p&gt;A growing SMB app hitting its first real concurrency problem faces a decision that's easy to get wrong in either direction: migrate to a client/server database too early and take on operational overhead the app doesn't need yet, or stay on SQLite too long and let write contention turn into user-facing timeouts. The right call isn't about which database is &amp;quot;better&amp;quot; in the abstract — SQLite and PostgreSQL are built to solve different problems, and picking between them comes down to reading a small number of concrete signals correctly rather than guessing at future scale.&lt;/p&gt;</description></item></channel></rss>