Abstract: Provided is a system and method for resiliency testing at a session level. A fault injection request is received from a client device associated with a user, via a user interface. The fault injection request defines an active impairment of one of a service or an endpoint with a blast radius restricted to a scope of the received fault injection request. The scope of the received fault injection request corresponds to a first session in a production environment or a lower environment. A client request is received from the client device within the blast radius of the active impairment. Based on the fault injection request and a persistence within the blast radius, the one of the service or the endpoint is impaired in the first session. A response, received from an entity associated with the one of the service or the endpoint, is transmitted to the client device.

Abstract: Provided is a system and method for resiliency testing at a session level. A fault injection request is received from a client device associated with a user, via a user interface. The fault injection request defines an active impairment of one of a service or an endpoint with a blast radius restricted to a scope of the received fault injection request. The scope of the received fault injection request corresponds to a first session in a production environment or a lower environment. A client request is received from the client device within the blast radius of the active impairment. Based on the fault injection request and a persistence within the blast radius, the one of the service or the endpoint is impaired in the first session. A response, received from an entity associated with the one of the service or the endpoint, is transmitted to the client device.

Abstract: The described technology is generally directed towards configuring a client device with client configuration data based on client context data. The configuration data can include endpoints of various services to which the client can connect that are appropriate for the client device based on the client context data, along with dimension information (route key values) for connecting to each such service. For example, a roaming client device can be given an endpoint and dimension information to connect to a content service in the roaming region, with a different endpoint and dimension information for communicating user information to a home region to which the user is affiliated. This facilitates single hop/reduced latency for content requests, and compliance with home regulations via a single hop to the home service.

Abstract: The described technology is generally directed towards configuring a client device with client configuration data based on client context data. The configuration data can include endpoints of various services to which the client can connect that are appropriate for the client device based on the client context data, along with dimension information (route key values) for connecting to each such service. For example, a roaming client device can be given an endpoint and dimension information to connect to a content service in the roaming region, with a different endpoint and dimension information for communicating user information to a home region to which the user is affiliated. This facilitates single hop/reduced latency for content requests, and compliance with home regulations via a single hop to the home service.

Abstract: The described technology is generally directed towards caching session state data on a client device, so that services called by the client device and other services can use the session state data without having to recollect such information from a server or servers that maintain the ground truth values for the session state data. The session state data can be divided into payload datasets based on domains or the like, so that only a relevant part of the session state data need be attached to a given communication, and/or updated when a session variable changes in some way. A payload dataset can be encoded or encrypted so that a service can verify the integrity of the payload dataset before using it, such as for service-to-service communication.

Abstract: The described technology is generally directed towards caching session state data on a client device, so that services called by the client device and other services can use the session state data without having to recollect such information from a server or servers that maintain the ground truth values for the session state data. The session state data can be divided into payload datasets based on domains or the like, so that only a relevant part of the session state data need be attached to a given communication, and/or updated when a session variable changes in some way. A payload dataset can be encoded or encrypted so that a service can verify the integrity of the payload dataset before using it, such as for service-to-service communication.

Abstract: The described technology is generally directed towards a system that facilitates interaction with an environment (e.g., a streaming service provider's platform) in a way that allows users with appropriate privileges simultaneous, privileged session-level experiences and experimental interactions with the environment's components. Via a session override, the technology allows a user associated with an authorized role to select among multiple, simultaneously available configurations to receive a different experience for a privileged session from that of any other general user. A privileged user can switch configurations as desired for different per-session experiences.

Abstract: The described technology is generally directed towards configuring a client device with client configuration data based on client context data. The configuration data can include endpoints of various services to which the client can connect that are appropriate for the client device based on the client context data, along with dimension information (route key values) for connecting to each such service. For example, a roaming client device can be given an endpoint and dimension information to connect to a content service in the roaming region, with a different endpoint and dimension information for communicating user information to a home region to which the user is affiliated. This facilitates single hop / reduced latency for content requests, and compliance with home regulations via a single hop to the home service.