Abstract: Improving load distribution and consistency is provided. A device intermediary to clients and servers can maintain bit values indicative of server availability stored in indices arranged in various levels. A lowest level comprises indices corresponding to a list of servers repeated multiple times. Each index in a higher level maps to a set of indices in a lower level. The device can receive a request from a client to access a server. The device can identify an index in a highest level. The device can determine a second index in the highest level that is after the index in the highest level and has a bit value indicating server availability. The device can identify an index in the lowest level mapping to the second index in the highest level. The device can select a server corresponding to the index in the lowest level.

Abstract: Improving distribution of traffic from clients to servers is provided. A device intermediary to a plurality of clients and a plurality of servers can receive a request from a client of the plurality of clients to access one of the plurality of servers. The device can determine a hash value based on at least a portion of the request received from the client. The device can identify an index of a plurality of indices listing the plurality of servers repeated a plurality of times in a deterministic shuffled order. The device can apply a cache array routing protocol (CARP) algorithm to a second plurality of servers listed in a subset of the plurality of indices around the index. The device can select a server from the second plurality of servers with a highest hash value based on the application of the CARP algorithm.

Abstract: Disclosed herein includes a system, a method, and a device for providing persistence across applications using a content switching server. A device can receive a first request from a client for a version of an application having different versions provided by one or more servers. The device can provide access to each version of the application via different load balancing virtual servers. A content switching virtual server of the device can select a load balancing virtual server to handle the first request for the version of the application. The content switching virtual server can generate a session identifier for a session between the client and the version of the application to persist the session with the selected load balancing virtual server for subsequent requests from the client for the version of the application.

Abstract: Systems and methods for domain name system (DNS) caching in a distributed processing engine include a first processing engine which may receive a DNS request for accessing a domain from a client. The first processing engine may generate a DNS query for a DNS controller based on the DNS request, The first processing engine may receive a DNS record corresponding to the domain from the DNS controller. The first processing engine may store data corresponding to the DNS record in cache of the first processing engine. The first processing engine may transmit a message including data corresponding to the DNS record for the domain to a second processing engine, to cause the second processing engine to store data corresponding to the DNS record in cache of the second processing engine.

Abstract: Systems and methods for domain name system (DNS) caching in a distributed processing engine include a first processing engine which may receive a DNS request for accessing a domain from a client. The first processing engine may generate a DNS query for a DNS controller based on the DNS request, The first processing engine may receive a DNS record corresponding to the domain from the DNS controller. The first processing engine may store data corresponding to the DNS record in cache of the first processing engine. The first processing engine may transmit a message including data corresponding to the DNS record for the domain to a second processing engine, to cause the second processing engine to store data corresponding to the DNS record in cache of the second processing engine.

Abstract: Described herein are systems and methods for updating configuration of a device based on changes to microservices. A device may receive a request via a desired state application programming interface (API) to update a configuration of the device to manage a desired set of instances of microservices. The device may identify from the request, a first set of endpoint information for each instance of a microservice in the desired set of instances of microservices. The first set of endpoint information may include an internet protocol (IP) address and port of an endpoint of a respective instance of the microservice. The first set or second set of endpoint information may include a weight for each instance of the microservice.

Abstract: Described embodiments provide systems and methods for routing client requests. A device may be arranged intermediary to a plurality of clients and a domain name system (DNS) controller. The device may generate a query for the DNS controller. The query may correspond to a service to be accessed by the clients. The device may receive, from the DNS controller, a response to the query. The response may include a value used by the device to route respective client requests for accessing the service to a corresponding version of a plurality of versions of the service. The device may receive, from a client, a client request for accessing the service. The device may route the client request to one of the versions of the service according to the value included in the response to manage traffic between various versions of the service.

Abstract: Described herein are systems and methods for updating configuration of a device based on changes to microservices. A device may receive a request via a desired state application programming interface (API) to update a configuration of the device to manage a desired set of instances of microservices. The device may identify from the request, a first set of endpoint information for each instance of a microservice in the desired set of instances of microservices. The first set of endpoint information may include an internet protocol (IP) address and port of an endpoint of a respective instance of the microservice. The first set or second set of endpoint information may include a weight for each instance of the microservice.

Abstract: Described embodiments provide systems and methods for routing client requests. A device may be arranged intermediary to a plurality of clients and a domain name system (DNS) controller. The device may generate a query for the DNS controller. The query may correspond to a service to be accessed by the clients. The device may receive, from the DNS controller, a response to the query. The response may include a value used by the device to route respective client requests for accessing the service to a corresponding version of a plurality of versions of the service. The device may receive, from a client, a client request for accessing the service. The device may route the client request to one of the versions of the service according to the value included in the response to manage traffic between various versions of the service.

Abstract: Disclosed herein includes a system, a method, and a device for providing persistence across applications using a content switching server. A device can receive a first request from a client for a version of an application having different versions provided by one or more servers. The device can provide access to each version of the application via different load balancing virtual servers. A content switching virtual server of the device can select a load balancing virtual server to handle the first request for the version of the application. The content switching virtual server can generate a session identifier for a session between the client and the version of the application to persist the session with the selected load balancing virtual server for subsequent requests from the client for the version of the application.

Abstract: Described herein are systems and methods for updating configuration of a device based on changes to microservices. A device may receive a request via a desired state application programming interface (API) to update a configuration of the device to manage a desired set of instances of microservices. The device may identify from the request, a first set of endpoint information for each instance of a microservice in the desired set of instances of microservices. The first set of endpoint information may include an internet protocol (IP) address and port of an endpoint of a respective instance of the microservice. The first set or second set of endpoint information may include a weight for each instance of the microservice.