4 ms·
Abstract a fleet of machines as single super computer sounds nice. But how about partial failures? It's something that a real stateful distributed system would
by uvdn7 5y ago
Abstract a fleet of machines as single super computer sounds nice. But how about partial failures? It's something that a real stateful distributed system would have to deal with all the time but a single host machine almost never deals with (do you worry about a single cacheline failure when writing a program?).
- marcosdumay 5y agoThere is a huge amount of research about distributed OSes (really, they were very fashionable at the 90's and early 00's). Plenty of people worked on this problem, and it's basically solved (as in, we don't have any optimal solution, but it won't be a problem on a real system).
- NavinF 5y agoIt’s “basically solved” in the sense that everyone gave up on distributed OSes and used k8s instead.
- zozbot234 5y agoK8s is doing distributed OS's on easy mode, supporting basically ephemeral 'webscale' workloads for pure horizontal scaling. Even then it introduces legendary amounts of non-essential complexity in pursuit of this goal. It gets used because "Worse is better" is a thing, not because anyone thinks it's an unusually effective way to address these problems.
- pjmlp 5y agoI see K8S as Application Servers for everyone, with containers replacing EARs, it certainly gets some WebLogic/WebSphere vibes when looking at those yml files and how we used to setup an Application Server cluster.
- marcosdumay 5y agoK8s just pushes the problem into the application layer, where every developer must solve it independently. It's not like it solves anything.