A) Get a Linode VM, put elastic search on it and have it load the text. Probably $20/month with that little text, tops.
B) Use something like KeyCDN to cache everything for long periods of time.
I doubt it'll cost $50/month.
A) Get a Linode VM, put elastic search on it and have it load the text. Probably $20/month with that little text, tops.
B) Use something like KeyCDN to cache everything for long periods of time.
I doubt it'll cost $50/month.
As a famous writer once said: "ain't nobody got time for dat."
Maybe not enough to afford a solution with more nines.
It's not about uptime, it's about the service existing at all. Even if you are fine with an hour downtime per day; at the end of that hour, you'll still need to bring it back online. The "aaS" part is about taking that load off. The nines are a corollary.
Concretely: a dedicated server leaves you with a lot of extra work. A packaged, managed service doesn't. E.g.: s3 for static files vs an nginx server on a VM. Even if they cost the same, s3 would still be a better option for git-scm.org.
If I had a choice between that and ~$1800/year?
If you don't want to do sysadmin work at the rate of ~$300/hr, that is your business.