Re:CapRover: Build your own PaaS
by pathseeker on Tuesday June 09, 2020 @03:34PM
(#23469976)
>web services that require high availability, redundancy and reliable backups. For these I just use Heroku.
How do you handle Heroku outages then?
Heroku outrage free was 99.9999%+ over the past 60 days[1], I'd have a hard time achieving this with a single dedicated server.
Re:CapRover: Build your own PaaS
by 1337shadow on Tuesday June 09, 2020 @09:07PM
(#23472778)
Do you really mean that you never had a server with 60 days uptime ? This is really insignificant to achieve, even a reboot per month is nothing, 99.9% of uptime is enough for 99.9% of projects, and a monthly reboot does not even get you close to that service level.
I am not affiliated nor haven't tried CapRover (for special reason of: coding my own for my tastytastes), but I would bet any standard system administrator could get a 99.9% uptime after the second month of production without particular effort (unless they don't know underlying technologies ie. "what a container" "what http" "what is namespace" "what iptables" ...)
Re:CapRover: Build your own PaaS
by pathseeker on Thursday June 11, 2020 @01:24PM
(#23491092)
I have a raspberry pi running on my desk that has been running for 60 days sitting on my desk with no outages. I don't even have a battery backup!
Re:CapRover: Build your own PaaS
by throwaway483284 on Thursday June 11, 2020 @04:05PM
(#23492822)
Maybe I am just an exception but I have 100% availability on one dedicated server for the last 2 years.
When you got applications that don't require high availability while needing a very low cost per CPU, dedicated servers just make sense. We are running a cluster of a few high-CPU dedicated servers for our data-science team, and it just makes sense: we don't need 99.99%+ availability, and the servers we rent are cheaper than the equivalent AWS storage cost alone ... The op cost of managing these is exactly the same as managing equivalent EC2 instances. We don't need backups either.
On the other side, we got some low-CPU web services that require high availability, redundancy and reliable backups. For these I just use Heroku. It's extremely reliable and easy to operate, while only costing about $100/month (a few hobby dynos + a fully managed PgSQL DB). Sure it's probably 5x more expensive than a dedicated server with 10x the performance, but I don't have to worry about backups, availability and scalability. And these apps just don't need this 10x faster CPUs anyway.