Here's a pipe dream I dreamed up after reading this post http://starmadedock.net/threads/galaxy-redesign-and-new-types-of-galaxy.21277/
A server clustering model would support this.
If you limited a server to generating a galaxy instead of a universe, you could have different galaxies operating on multiple servers.
This would require a central economic/cluster management server for these servers to synchronise with, much like VMware do with vSphere/ESX clusters and Citrix do with XenServer. It would cut down on processing an entire universe, leaving the processing distributed across multiple physical machines.
My earlier suggestion for an interserver warpgate or warp capability could be modified to accommodate a multi-galaxy/server cluster scenario if you had a Starmade server instance per galaxy. I see it operating the same way the separation between sectors works, but you engineer it to somehow seamlessly transition you from one server to another, kind of how vMotion works in VMware's vSphere product. Pretty much Starmade server clustering is where I'm heading, where the ecomonic and most likely entity positioning server would be the VMware vCenter equivilant, handling the multiple hosts/galaxies.
Example Components;
Starmade Server Cluster made of...
Starmade Centre or Managment Server
- Keeps track of GPS of galaxies within a Starmade Server cluster
- Keeps track of inter-galaxy economics
- Any inter-galaxy comms, entity relationships etc
Starmade Server
- Has a defined size like you do with sectors and is merely a galaxy.
- Has built in Entity tracking like normal
- Has access to GPS on Starmade Centre/Mgmt Server for relative interaction with other galaxies in the universe, like warp gates etc
- When transitioning from one galaxy to another, you go through a type of vMotion (VMware) from server to server. Have a transition effect. Problem may be when you have armada's or someting, but I'm sure something could be worked out.
Starmade Client
- Much the same as existing, but connects to this new clustering server environment via the Starmade Centre/Mgmt Server
A server clustering model would support this.
If you limited a server to generating a galaxy instead of a universe, you could have different galaxies operating on multiple servers.
This would require a central economic/cluster management server for these servers to synchronise with, much like VMware do with vSphere/ESX clusters and Citrix do with XenServer. It would cut down on processing an entire universe, leaving the processing distributed across multiple physical machines.
My earlier suggestion for an interserver warpgate or warp capability could be modified to accommodate a multi-galaxy/server cluster scenario if you had a Starmade server instance per galaxy. I see it operating the same way the separation between sectors works, but you engineer it to somehow seamlessly transition you from one server to another, kind of how vMotion works in VMware's vSphere product. Pretty much Starmade server clustering is where I'm heading, where the ecomonic and most likely entity positioning server would be the VMware vCenter equivilant, handling the multiple hosts/galaxies.
Example Components;
Starmade Server Cluster made of...
Starmade Centre or Managment Server
- Keeps track of GPS of galaxies within a Starmade Server cluster
- Keeps track of inter-galaxy economics
- Any inter-galaxy comms, entity relationships etc
Starmade Server
- Has a defined size like you do with sectors and is merely a galaxy.
- Has built in Entity tracking like normal
- Has access to GPS on Starmade Centre/Mgmt Server for relative interaction with other galaxies in the universe, like warp gates etc
- When transitioning from one galaxy to another, you go through a type of vMotion (VMware) from server to server. Have a transition effect. Problem may be when you have armada's or someting, but I'm sure something could be worked out.
Starmade Client
- Much the same as existing, but connects to this new clustering server environment via the Starmade Centre/Mgmt Server