Requirement for directing client requests to a GRM L7 server

Use a standard DNS nameserver

Advantage

• This is a simple solution.

Disadvantages

• There is no way to guarantee that the GRM L7 server to which the DNS nameserver redirects requests is the closest one to the client.

  For example, if one GRM L7 server is in Australia and another is in the United States, the DNS nameserver round-robin process might direct requests from clients in the United States to the GRM L7 server in Australia.

• The GRM L7 server can become overloaded if all client requests are sent to the same GRM L7 server

See Using a DNS nameserver to locate a GRM L7 server.

Deploy a GRM DNS server

Advantages

• The GRM DNS server acts as an intelligent means of locating the closest GRM L7 server to the clients.
• The GRM DNS server can also be used to monitor the health of the GRM L7 servers.

Disadvantages

• This solution is more complicated than using only a DNS nameserver.
• This solution requires additional NetCache appliances.

See Using a DNS nameserver to locate a GRM L7 server.

Use a locator solution in your network infrastructure

Advantage

• An existing locator device in the network infrastructure can be used. Some locator devices provide sophisticated features, for example, features for load balancing over GRM L7 servers.

Disadvantages

• You must rely on the existing network infrastructure.
• You must have devices in your network infrastructure to support this function.

See Using the network infrastructure to locate a GRM L7 server.

Use a proxy.pac file

Advantage

• This solution is inexpensive, scalable, and easy to implement.

Disadvantages

• Client browsers must be manually configured to point to the proxy.pac file on the GRM L7 server that is closest to the clients.
• Load balancing must be programmed into the proxy.pac file (for example, hash on URL).

See Using a proxy.pac file with a GRM L7 server.