DynConD – Dynamic Content Delivery Network Service is a
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?
What is the basic idea behind DynConD?
If a client can access some network service located on two or more servers he can select:
DynConD uses Dynamic Server Selection (DSS) process because:
Network Distance Measurement
Yes, between client and available servers
Global Server Load Balancing
Service Response Time Measurement
Server Load Measurement
API
Instant Failover
High Availability
Do you know an article comparing DynConD to other products?
Suggest a link to a post with product alternatives.
This is an informative page about DynConD. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.