Linux-ha High-availability open source Solution keepalived VS Heartbeat selection __linux

Two high available open source solutions: keepalived and Heartbeat. Both are very popular, but the difference is still very large, and now the trial process of the experience and related knowledge points simply summed up for everyone to choose the time of the reference.

1keepalived use simpler: From the installation, configuration, use, maintenance and other angles of comparison, keepalived are much simpler than heartbeat, especially heartbeat
2.1.4 after split into 3 subprojects, installation, configuration, use are more complex, especially when the problem, do not know what the specific subsystem problem, and keepalived only 1 installation files, a configuration file, the configuration file is also a lot simpler;

2Heartbeat function is more powerful : heartbeat Although complex, but more powerful, supporting tools more complete, suitable for large-scale cluster management, and keepalived mainly for cluster switching, basically no management functions;

3) different protocol : keepalived use VRRP protocol for communication and election, heartbeat use heartbeat for communication and election; Heartbeat in addition to walk the network, but also through the serial port communication, seemingly more reliable;

4 usage is basically similar : If you want to design a highly available solution based on both, you will end up with a custom script based on your business needs, keepalived scripts have no constraints, you can write whatever you want; Heartbeat scripts are bound to support service
Start/stop/restart this way, and Heartbeart provides a lot of default scripts, simple binding IP, the launch of Apache and other operations have been;

Use of recommendations: priority to use keepalived, when keepalived not enough to choose heartbeat