| Cluster & Loadbalancing |
Managed Services |
Also a little IT-failure could mean a considerably high financial loss for companies.
To minimize the risk of failures and to guarantee a high-availability we develop a suitable concept together with the client and we implement it.
|
 Monitoring
Backup
Security
|
| |
Cluster
To be able to react on the total failure of a server we recommend the setup of a cluster. A cluster consists of two servers or more.
In this case the active server (Master) answers the inquiries of the users and the second server (Slave) serves as silent backup of the first server. Only when a failure of the active server is located the Slave immediately takes on the task of the Master automatically.
The data have to be mirrored in regular intervals, since both servers have to possess the identical data pool in order to be able to backup themselves.
Loadbalancing
For big applications, to which several thousands of users access at the same time, we recommend the use of a load-balancer. The load-balancer dispenses the users on each server and it makes the environment highly scalable because, if required, there can simply be fitted in further servers.
If you choose load-balancing we recommend you the use of a cluster as backup because otherwise the load-balancer poses a security risk referred to as a single-point of failure.
During the conception and the run, trust in the experience of InterLake of high-availability solutions. We run cluster-architectures with up to 15 servers which are adjusted specifically to the individual parameters of every single client.
|
|
|
|
