Remix clone Hacker News

> no downtime except when it restarts for updates.

This sounds a little like saying "all of North America except the U.S."

I don't think people are worried about random breakdowns on a single VPS, but scheduled updates are still downtime, and downtime causes revenue loss regardless of why it happened.

Any time a service is important enough I ask for two servers and a load balancer specifically to handle deployments and upgrade windows transparently. But! I agree services are usually less important than people think.

▲

RadiozRadioz 2 days ago | parent [-]

> upgrade windows

Ok, that explains this and the above comment. The last time I had to restart anything to apply an OS update was when I moved to a new RHEL LTS version, the lifespan of which is about 10 years. And there are many ways to do similar GNU/Linux upgrades without a restart at all.

Does Windows Server really need to restart for updates like normal Windows? If so, that's hilariously crap and I'm glad I've never had to touch it.

Edit: not saying a single VPS is fine if it's GNU/Linux, just remaking on the "restart to update" thing they mentioned

	▲	HappMacDonald 2 days ago \| parent \| next [-]
		> to handle deployments and upgrade windows transparently GP might have meant "upgrade: Windows(tm)", or he might have meant "windows of time which we have allocated to upgrading the server", and on my first reading I interpreted the second without a single shred of thought towards the possibility of the first.
	▲	stackskipton 2 days ago \| parent \| prev [-]
		Most people have to apply patches and if they don't install kpatch, there is generally a restart required to make sure everything is using new versions. Yes, you can restart all the services that probably slightly less downtime to full reboot on most VPS these days.