In this chapter, we showed various ways of distributing application load across a set of nodes. This is referred to as load balancing.
Load balancing requires a web server, such as Apache, which directs traffic to your various application servers.
In the first half of this chapter, we illustrated how to use the
mod_proxy libraries in WildFly. The
mod_jk library requires some configuration on both the HTTPD side and the AS side. The
mod_proxy library is a more immediate solution and a preferred solution when using WildFly as it requires simply configuring the end points on the HTTPD side.
In the second half of the chapter, we looked at the recommended approach to load-balance calls between applications using
The main advantage of using
mod_cluster versus traditional load balancers is that it does not require a static list of worker nodes, rather, it registers application servers and their applications dynamically using a multicast-based advertising mechanism.