<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Simplicity on Bootstrapping.org</title>
    <link>https://bootstrapping.org/tags/simplicity/</link>
    <description>Recent content in Simplicity on Bootstrapping.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bootstrapping.org/tags/simplicity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SQLite vs MySQL for Small Sites: When Simplicity Wins</title>
      <link>https://bootstrapping.org/2026/04/08/sqlite-vs-mysql-for-small-sites-when-simplicity-wins/</link>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://bootstrapping.org/2026/04/08/sqlite-vs-mysql-for-small-sites-when-simplicity-wins/</guid>
      <description>&lt;p&gt;The default assumption in web development is that serious applications run on serious databases, and serious databases means a separate server process, connection pooling, user management, and a configuration file that will eventually be wrong in a way that takes an afternoon to diagnose. MySQL and PostgreSQL are excellent databases. They are also, for the median small site, a solution in search of a problem — infrastructure designed for concurrency, scale, and replication requirements that don&amp;rsquo;t exist at any traffic level the site will realistically see for years.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
