Notably, the SQLite website is (as far as I can see) read-only. So it's great if all you need is a SQL read API atop your structured data (and 100k hits/day is probably only limited by the filesystem/os since SQLite isn't a server). But you're setting yourself up for headaches by using SQLite if you need simultaneous read/writes combined with HA.
I think some cloud stuff is overpriced, but RDS easily pays for itself in my case.
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. 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.That said, I think it's more meant to be an anecdotal rule of thumb to tell people "you're not Google, SQLite will work for most teams".
It really depends. Also, configuring everything right gets hard. Most don't even think to do RAID over a few block storage devices, but that's something that comes with cloud storage. That doesn't count HA and other issues before getting to the application layer.
It's something that unless you're paying a full-time DBA, you are probably better off buying as a service. It's one of the few holes in DO's offerings and I'm very happy to see this.
[1] https://www.sqlite.org/whentouse.html under "Websites" section