Hitachi

Hitachi Application Server V10 User's Guide (For Windows® Systems)


2.3.2 System configurations that ensure availability and performance

This subsection explains system configurations that use Application Server to ensure availability and performance. As typical examples of such system configurations, this subsection describes the characteristics of the following configurations: 1) configuration that uses a hardware load balancer, 2) configuration that uses a generic software load balancer, 3) configuration that uses the Web Server load balancing function, and 4) configuration that uses cluster software.

Configuration that use a hardware load balancer

This type of configuration uses a hardware load balancer to distribute requests evenly to multiple Java EE servers. This type is suitable for mission-critical systems with a large number of transactions. This type can ensure high reliability and availability.

[Figure]

Configuration that uses a generic software load balancer

This type of configuration uses a generic software load balancer to distribute requests evenly to multiple Java EE servers. This type is suitable for systems with a large number of transactions. This type ensures reliability and availability without using expensive load balancers.

[Figure]

Configuration that uses the Web Server load balancing function

This type of configuration uses the Web Server load balancing function to distribute requests evenly to multiple Java EE servers. This type is suitable for systems with a large number of transactions. Using the load balancing function of Web Server can ensure reliability and availability at low cost.

[Figure]

Configuration that uses cluster software

This type of configuration uses cluster software to create a cluster configuration where multiple Java EE servers are installed on active and standby nodes. This type is suitable for systems with few transactions where only a single machine can process requests. This type of configuration prepares a standby node in case of a fault occurrence, and this node can also be used effectively as a development or test environment during normal operations.

[Figure]