<p><pre><code> "The SQLite website (https://www.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.
Each dynamic page does roughly 200 SQL statements. [...]"
</code></pre>
Wait... What? They're saying that their dynamic pages are executing 200 SQL statements per request?<p>Off-topic: I enjoyed reading this article which was posted here a while ago <a href="http://www.sqlite.org/testing.html" rel="nofollow">http://www.sqlite.org/testing.html</a>
<i>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.</i><p>I am curious to know how many people here solely use SQLite to power the back-end of their web application(s), especially when the page states, "<i>SQLite does not compete with client/server databases.</i>"<p>(Or is the page referring to content-management-system-type websites?)
There's also mbtiles, which is a standard way of storing map tiles in an sqlite database in blob fields.<p><a href="https://www.mapbox.com/guides/an-open-platform/#storing-tiles" rel="nofollow">https://www.mapbox.com/guides/an-open-platform/#storing-tile...</a><p>you can have sqlite databases that are gigs in size and perform great.
Can anybody speak to their experience using sqlite for data analysis purposes?<p>Am I wrong in thinking it's just plain old row oriented storage and not something more aggregate oriented?
Neat. I've also used an in-memory SQLite db for testing ActiveRecord models.<p>Also, the same list if uses can be applied to nedb as a lightweight alternative to MongoDB.