DynConD VS Oracle WebLogic

DynConD – Dynamic Content Delivery Network Service is a

• Client-side Global Server Load Balancer
• DNS-based Client-Server service for optimal server selection and server load management
• The ultimate choice for the fastest delivery of network services to clients

DynConD client-side GSLB is used by replicated and distributed network services for better user experience and global server load balancing. The client selects the optimal server independently, based on a measured network distance between client and servers (in contrast to commonly used imprecise geographic proximity) and current server load or service response time.

When can DynConD be used?

• DynConD can be used when more than one server is available to provide a network service
• DynConD can be used when a client uses Android,iOS OS,Windows or Linux apps

What is the basic idea behind DynConD?

If a client can access some network service located on two or more servers he can select:

• The server with the shortest network distance (RTT)
• The server with the fastest service response time
• The server with the least load What kind of server selection process does DynConD use?

DynConD uses Dynamic Server Selection (DSS) process because:

• Each client has a unique network distance to each particular server
• The response time of the server service changes over time
• Server load and/or service response time is not constant