4 ms·
If uptime is critical and you don't want this to be a full time job then don't do it... Opt for PaaS. But for me uptime isn't critical, I can happily be down f
by buro9 5y ago
If uptime is critical and you don't want this to be a full time job then don't do it... Opt for PaaS.
But for me uptime isn't critical, I can happily be down for a few days if needed. It hasn't happened once yet but I can tolerate it were it to happen.
Plus this is how I learn. By doing it I learn how to do it and what should be considered. When it goes wrong I learn how to avoid that in future and what I should do to minimise risk of it recurring.
I find the database to be the easiest past to manage, it's file storage and availability of that which I outsource to AWS S3. The volume of that is harder for me to trivially solve. Self hosting Ceph seems more intimidating. Postgres is easy though.
- sam_lowry_ 5y agoI had a similar setup, only with MySQL as the database since 2003. Started on a server in a closet of my own apartment, then moved to Leaseweb, then Hetzner. The project had its highest point some 14 years ago, with well over 1mln page views per month, but I could still fit it on a single bare metal server. As the project started to fade out, I moved to Hetzner Cloud to reduce the cost of standby infrastructure. It was down for 4 hours in a row several times over these 18 years, but otherwise the uptime was close to six sigma (under 3 hours per year). It's surprising how rock solid hosting providers are. Can't imagine hosting anything substantial on AWS after all these years.