From Dr. Richard Hipp:<p>If you look at the [Project Age](https://sqlite.org/src/stat) within
the next 23 hours or so, you'll see that it says exactly "*25 years*".<p>Our expectation is to continue enhancing SQLite for many years to come and
to support it actively for at last 25 more years.
"SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic.<p>The SQLite website (<a href="https://sqlite.org/" rel="nofollow">https://sqlite.org/</a>) uses SQLite itself, of course, and as of this writing (2015) it handles about 400K to 500K HTTP requests per day, about 15-20% of which are dynamic pages touching the database. Dynamic content uses about 200 SQL statements per webpage. This setup runs on a single VM that shares a physical server with 23 others and yet still keeps the load average below 0.1 most of the time" - The documentation<p>I use sqlite as the database for my blog - <a href="https://www.rxjourney.net/" rel="nofollow">https://www.rxjourney.net/</a><p>For most of us, it's all we need.