3 ms·
It sounds like you're interested in 'Single System Image' distributed systems. And hopefully that keyword helps you find more of them to look into. It's a lot
by toast0 4y ago
It sounds like you're interested in 'Single System Image' distributed systems. And hopefully that keyword helps you find more of them to look into.
It's a lot harder to put together something like that than a more conventional distributed system based on multiple independent servers. I don't think there's a large benefit really, either, as there's plenty of ways to operate similarly across independent servers.
The biggest problem with single system image systems is around managing failure domains. Conventional systems don't have portions of the memory and CPU and X go offline. And when those things do go offline, how do you know if it'll come back with the same state (momentary network disruption) or come back with a loss of state (unscheduled reboot) or not at all (something broke). Or, actually worse, how do you handle when the networking gets degraded and suddenly you have half the throughput or twice the latency or both? These are real issues that need to be solved in any type of distributed system, but it's got to be a lot harder when your program is not aware of the node boundaries it's crossing; it's hard already in a conventional distributed system where nodes are aware of the network, but not of the network boundaries (ex: nodeA wants to talk to nodeB or nodeC, but doesn't know that connectivity to nodeB is congested, so it just divides load between B and C, contributing to the congestion)