alt Hacker NewsThe wildest part is they’ll take those massive machines, shard them into tiny Kubernetes pods, and then engineer something that “scales horizontally” with the number of pods.
Replies
jesse__ • yesterday at 5:46 PM
Yeah man, you're running on a multitasking OS. Just let the scheduler do the thing.
➕ show 3 replies
andai • yesterday at 6:07 PM
I had to re-read this a few times. I am sad now.
cyberpunk • yesterday at 7:13 PM
To be fair each of those pods can have dedicated, separate external storage volumes which may actually help and it’s def easier than maintaining 200 iscsi or more whatever targets yourself
ahartmetz • yesterday at 6:01 PM
I think my brain hurts
jayd16 • today at 12:03 AM
I mean, a large part of the point is that you can run on separate physical machines, too.
This is especially aggravating when the os inside the container and the language runtimes are much heavier than the process itself.
I've seen arguments for nano services (I wouldn't even call them micros services), that completely ignored that part. Split a small service in n tiny services, such that you have 10(os, runtime, 0.5) rather than 2(os, runtime, x).