4 ms·
Because it's hard to keep services up and most shops aren't especially competent. Having a process running for 1511 days does not mean a service has 1511 days
by caturopath 5y ago
Because it's hard to keep services up and most shops aren't especially competent.
Having a process running for 1511 days does not mean a service has 1511 days of uptime -- there are a ton of places stuff can go wrong.
- iso1631 5y agoRunning a simple service on a single server for a year without issue is not hard. Running a service like slack is hard, but modern HN attitude is if you can't scale to a billion users your architecture is rubbish.
- caturopath 5y agoRunning a service isn't hard. Going a year without any sort of outage is. For example, if you're just serving from one place, any network outage between the users and that place will be an outage -- seamless failover is pointlessly hard and very few shops do this for their internally-hosted services.
- iso1631 5y agoDepends how you define a network outage. One of my transatlantic circuits has been a bit ropey - had a 2 second outage on it a couple of nights ago, does that count as a network outage? If a user has a local network problem, that's not a loss in the service. If multiple users do that's an issue. My home broadband went out for 3 minutes at 23:33:43 GMT on May 13th, but then I wouldn't run a service needing 24/7 on my home broadband. My frickin nasdrive has a better uptime than slack.