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*".
Our expectation is to continue enhancing SQLite for many years to come and to support it actively for at last 25 more years.
chistev•8mo ago
The SQLite website (https://sqlite.org/) 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
I use sqlite as the database for my blog - https://www.rxjourney.net/
For most of us, it's all we need.
DimmieMan•8mo ago
I have a multi tenanted application dealing with time series data in different time zones and I use Postgres for that.
For a blog and most applications I go SQLite too but I think there’s a good argument that often gets left out that complexity might make Postgres a better choice sometimes even on low traffic.
Between the two I think it is all >90% of us need.
sgbeal•8mo ago
Almost. The main site is static HTML except for the site search (which of course uses SQLite). However, several of its top-most paths are CGIs based on the Fossil SCM, so SQLite: /forum, /src, /docsrc, etc.