Your site may start with a modest membership. But it is reassuring to know that as your site grows in size, WebCrossing Core grows with you to support even millions of members without speed or service degradation. That is why WebCrossing servers have always been the choice of large companies, universities and organizations with large membership and extraordinary server load requirements.
Setting up mirrored and distributed servers is easy, via the WebCrossing Core Web-based Control Panel. You can connect WebCrossing Core servers in any mirrored or distributed configuration needed, for hardware redundancy, load balancing and almost unlimited scaling. Messages propagate throughout mirrored servers in milliseconds.
The diagram above shows three mirrored servers, but you are not limited to three. There is no fixed limit. One of our larger customers report experiencing just a 3% load on the source server running with three mirrors, as in the diagram above, where each mirror is running at 30% capacity. So if the mirrors were fully loaded with traffic we could estimate that the source would be at 9% usage. This places the practical limit at 20-30 mirror servers for each cluster, and additional clusters may also be added as necessary. To enable you to decide on the best configuration for your large site, WebCrossing Core includes built-in stress-testing tools so you can simulate various loads on your own hardware and network infrastructure, with read/write/chat combinations and various numbers of simulated clients.
Mirroring is possible with a single WebCrossing Core license so long as the user directory and database are the same. Each group of mirrored servers is considered a single "cluster." And because no expensive third-party database is required, this kind of configuration is not only economical, it is easy to set up and maintain because the native WebCrossing Core database is included with each server instance.
WebCrossing Core servers can also be broken up and distributed, sharing a common user directory, but separate discussion contents, as in the following diagram.
Distributed servers provide linear scalability of database size. The diagram shows just two server clusters, but any number of clusters can be distributed in this way. Users are automatically tracked as they move from database cluster to database cluster. Each cluster itself can be comprised of multiple mirrored servers, as described above, allowing for just about any server topology imaginable.
Setting up mirrored and distributed servers is easy, via the WebCrossing Core Web-based Control Panel. You can connect WebCrossing Core servers in any mirrored or distributed configuration needed, for hardware redundancy, load balancing and almost unlimited scaling. Messages propagate throughout mirrored servers in milliseconds.
Mirroring is possible with a single WebCrossing Core license so long as the user directory and database are the same. Each group of mirrored servers is considered a single "cluster." And because no expensive third-party database is required, this kind of configuration is not only economical, it is easy to set up and maintain because the native WebCrossing Core database is included with each server instance.
WebCrossing Core servers can also be broken up and distributed, sharing a common user directory, but separate discussion contents, as in the following diagram.