The problem with this approach is the need to have multiple worlds. That work fine if you want to have multiple mini-game worlds running, but what if you want to have an enormous survival server? Having multiple worlds for single purpose would be painful, and wouldn't mitigate single points of failure. "oh no survival-40 is down again, can't reach my house 
"
Besides that, you would still not have the load optimally balanced. Let's say you have 10 minigames servers, but then only 2 are popular at daytime and other 3 are popular night time. You can't scale instances up and down on an environment like this.
It becomes a waste of resources in no time.
Clustering provides optimal load balancing ($), scaleability and protection from single points of failure. Also, it's a hell lot easier to manage.
I understand this is not a priority ATM, we need feature parity with latest releases, better mob AI and more plugins after all, but take this into consideration once cuberite becomes mainstream.
Let me better explain the master-slave approach I described on the other post: everything that can be done asynchronously would be handled by all servers and at the same time. Like chat, player movement, block placement, etc. Things that absolutely need to be done synchronously, like redstone processing, would be done by any one server at a time. If this server dies, any other one is promoted to be the redstone-master. Multiple masters would co-exist at the same time. For instance, server-a is the redstone-master, but server-b is the tnt-master.
"Besides that, you would still not have the load optimally balanced. Let's say you have 10 minigames servers, but then only 2 are popular at daytime and other 3 are popular night time. You can't scale instances up and down on an environment like this.
It becomes a waste of resources in no time.
Clustering provides optimal load balancing ($), scaleability and protection from single points of failure. Also, it's a hell lot easier to manage.
I understand this is not a priority ATM, we need feature parity with latest releases, better mob AI and more plugins after all, but take this into consideration once cuberite becomes mainstream.
Let me better explain the master-slave approach I described on the other post: everything that can be done asynchronously would be handled by all servers and at the same time. Like chat, player movement, block placement, etc. Things that absolutely need to be done synchronously, like redstone processing, would be done by any one server at a time. If this server dies, any other one is promoted to be the redstone-master. Multiple masters would co-exist at the same time. For instance, server-a is the redstone-master, but server-b is the tnt-master.