undefined | Better HN

0 pointsmoonbug5y ago0 comments

>Arguably, no one should be running a server that long in 2020.

That's mental.

0 comments

My read on that is that you should be treating your servers as disposable and ephemeral as possible. Long uptimes mean configuration drift, general snowflakery, difficulties patching, patches getting delayed/not done, and so forth.

Ideally you'd never upgrade your software in the usual way. You'd simply deploy the new version with automated tooling and tear down the older.

hibbelig5y ago

I don't get this. If there are many servers, sure. But if it's something that runs on a single box without problem, why on earth should I tear it down?

Also, "running a server for ten years" does not need to mean that it has ten years of uptime. I think that wasn't meant.

moonbugOP5y ago

Ten years of uptime seems neither an unreasonable nor unattainable requirement. There's more to computers than mayfly web startups.

1 more reply

NDizzle5y ago

"Ideally" - that's the problem. I have half a dozen long tail side projects running right now on Centos 7, and a few still on Centos 6.

Do you have any idea how much effort it is to change everything over to "treating your servers as disposable"?! It's going to eat up a third (to half) of my "fun time" budget for the foreseeable future!

effie5y ago

Exactly, young devs here are completely out of touch with operations. Of course ideally something like standard 1TB HDD+32GB RAM system would be upgraded to newer OS and apps version by a central tool in 2hours, but we don't such FM technology yet.

cat1995y ago

> automated tooling

the 'usual way' is automated tooling

j / k navigate · click thread line to collapse