3 ms·
You know that some people work on servers that are stateful? Not everyone use REST type of transport where a failed node is ok because the lb will route traffic
by Thaxll 8y ago
You know that some people work on servers that are stateful? Not everyone use REST type of transport where a failed node is ok because the lb will route traffic to another place. Your solution doesn't work for things like game servers.
- weberc2 8y agoPresumably you just drain the servers running the old version as games end and migrate traffic to the servers running the new version?
- viraptor 8y agoEven stateful services like game servers could be organised to handle losing a node. It's harder to do and you need some state replication in place. (versioned state if you want to do upgrades that way) It may not be cost effective to do so. But the possibility is there. I worked on a plan to have live migration of multiparty phone calls between data centres in realtime. The tech is available. But your planning outcome may be: it's cheaper to make single node more stable and deal with the occasional failure. "Stateful" only means you need to care about the state being moved. Things like Java hotswap, Erlang live code reload, and your custom solutions can handle that.
- otterley 8y agoDo you run game servers? They absolutely have failover capability.