Abstract: Systems and methods for failover monitoring using dynamic traffic tagging are disclosed. In an example method, a computing device outputs failover information including a designation of a current failover location. The computing device receives, from a server device, a failover status message indicating that the server device received a request message including the current failover location. The computing device then outputs a second failover information including a second designation of a second network location as the current failover location. The computing device receives from the server device, a second failover status message indicating that the server device received a second request message including a network location other than the current failover location. The computing device then outputs a failover failure notification and outputs a command to cause a corrective action.

Abstract: A system and method for failover for cloud-native applications, such as cloud-native video-conferencing services, that includes a software agent that monitors the health of services executing on servers. An agent monitors predefined metrics of a service and sends alerts to a plan-execution system when a monitored metric fails to satisfy a predefined condition. The plan-execution system applies predefined rules to received alerts to determine whether a service is failing. The plan-execution system instructs a command center to redirect client requests for a failing service to a failover service.

Abstract: Techniques for parallel execution component initialization using static dependency analysis are disclosed. In an example method, a computing device receives a set of program code comprising execution components. The computing device generates a dependency graph based on a static analysis and determines a subset of the execution components that do not depend on any other execution component of the execution components. The computing device configures an initialization thread pool to initialize in parallel a plurality of the subset of the execution components. Responsive to a first execution component of the subset of the execution components completing initialization, the computing device determines a second execution component that depends on the first execution component and does not depend on any other uninitialized execution components of the execution components or any of the subset of the execution components initializing.

Abstract: An initialization function is configured to modify respective bytecode of classes associated with transport layer functionality to enable logging of first data associated with transport layer requests. A discrepancy between at least one of the transport layer requests and application services layer requests is identified by analyzing the first data logged by the initialization function and second data associated with the application services layer requests, where the discrepancy indicates an instance where a transport layer request lacks a corresponding application services layer request. Data related to a first access mechanism for accessing a database and data related to a second access mechanism for accessing the same database may be logged.

Abstract: Systems and methods of message filtering in a multi-region multi-active architecture are provided. A client device receives a data message, the data message comprising a region tag and an account tag. The client device determines whether the region tag corresponds to a region server assigned to serve the client device. In response to determining the region tag corresponds to the region server assigned to serve the client device, the client device determines whether an account identification (ID) associated with the client device matches the account tag of the data message. In response to determining the account ID matches the account tag, the client device consumes the data message.

Abstract: Systems and methods of message filtering in a multi-region multi-active architecture. A client device via a client application receives a data message associated with a topic subscribed by the client application from an application service provider. The data message includes a region tag associated with a region server producing the data message and an account tag representing a group of client accounts associated with the data message. The client device determines whether the region tag corresponds to a home region server assigned to the client application. In response to determining the region tag corresponds to the home region server assigned to the client application, the client device determines whether an account identification (ID) corresponding to the client application matches the account tag in the data message. In response to determining the account ID matches the account tag, the client device consumes the data message.