Conclusion For each of the above mentioned points of discussion, a different approach must be taken. The important thing to notice here is that all clusters rely on more than one node to carry out their tasks. As such, this is the common starting point for all cluster setups. Clusters are usually being considered when one type of resource is no longer sufficient, or when a single system can no longer keep up with the demands. This means that it is often too late to prevent the shortage situation with the aid of a cluster, a very complex technical undertaking that requires careful planning and even more careful testing before it becomes ready and stable enough to append to an already crippled network. This is the most frightening side of clustering. Implementing a very complex system on short notice with high expectations can be frustrating.

Note: Clusters are really complex; there is no doubt about that. However, if the components that make up the cluster are understood correctly, only minor issues should come between the initial project and the resulting solution. Nothing can compensate for the cluster engineer’s experience.

It is imperative to correctly estimate and manage available resources, as a cluster has the bad habit of consuming as much as it can out of every available resource.