3 ms·
> MySQL and Postgres are larger than Sqlite by more than an order of magnitude. But they're still small, since you can run them on the smallest available cloud
by crazygringo 2y ago
> MySQL and Postgres are larger than Sqlite by more than an order of magnitude.
But they're still small, since you can run them on the smallest available cloud VM's and have plenty of memory/CPU/disk left over for webserving.
> What do you get in exchange for all those lines of code? Do you actually need the extra functionality?
The ability to scale beyond a single webserver.
It's just as easy to use Postgres as SQLite, but by choosing SQLite you've made life much more complicated for yourself if you ever need to scale to two servers. Why would you inflict that headache upon yourself?
- kbolino 2y agoThe smallest available (burstable) instance type on AWS (t2.nano) has 1 vCPU, 3 CPU credits/hour (~= 5% average CPU utilization), and 512 MB of RAM. I don't think you're going to run very much on there and definitely not with room to spare.
- crazygringo 2y agoYou can run MySQL on that perfectly fine, together with Apache and PHP or something. If you've just got a small website without tons of traffic, it's no problem at all.