Disclosed embodiments are directed at systems, methods, and architecture for operating a control plan of a microservices application. The control plane corresponds with data plane proxies associated with each of a plurality of APIs that make up the microservices application. The communication between the data plane proxies and the control plane enables automatic detection of service groups of APIs and automatic repair of application performance in real-time in response to degrading service node conditions.

Technologies for switching network traffic include a network switch. The network switch includes one or more processors and communication circuitry coupled to the one or more processors. The communication circuity is capable of switching network traffic of multiple link layer protocols. Additionally, the network switch includes one or more memory devices storing instructions that, when executed, cause the network switch to receive, with the communication circuitry through an optical connection, network traffic to be forwarded, and determine a link layer protocol of the received network traffic. The instructions additionally cause the network switch to forward the network traffic as a function of the determined link layer protocol. Other embodiments are also described and claimed.

A method for distributing connections to mobility management node instances includes publishing IP addresses for receiving connection requests and ingress messages from RAN nodes. The method further includes maintaining connection loading measurements of the mobility management node instances, receiving a connection request message generated by a RAN node for initiating a connection with one of the mobility management node instances, applying a connection distribution algorithm to select a mobility management node instance to handle the connection request message, and creating an association between an IP address of the selected mobility management node instance and an IP address and port of the RAN node extracted from a source IP address and source port field of the connection request. The method further includes forwarding the connection request message to the selected mobility management node instance.

Active-active standby is maintained for communication sessions using web connections between two active session zones and a standby session zone, for example, in the event of a failure. The first active session zone is located at a first datacenter, the second active session zone is located at a second datacenter, and the standby session zone is located at a third datacenter. In the event of a failure at a first active session zone at the first datacenter, a failover to the second active session zone at the second datacenter is performed. In the event of a failure at both active session zones, a failover to the standby session zone at the third datacenter is performed.

Active-active standby is maintained for communication sessions using web connections between two active session zones and a standby session zone, for example, in the event of a failure. The first active session zone is located at a first datacenter, the second active session zone is located at a second datacenter, and the standby session zone is located at a third datacenter. In the event of a failure at a first active session zone at the first datacenter, a failover to the second active session zone at the second datacenter is performed. In the event of a failure at both active session zones, a failover to the standby session zone at the third datacenter is performed.

Active-active standby is maintained for communication sessions using web connections between two active session zones and a standby session zone, for example, in the event of a failure. The first active session zone is located at a first datacenter, the second active session zone is located at a second datacenter, and the standby session zone is located at a third datacenter. In the event of a failure at a first active session zone at the first datacenter, a failover to the second active session zone at the second datacenter is performed. In the event of a failure at both active session zones, a failover to the standby session zone at the third datacenter is performed.

System and methods for enforcing service level agreements (SLAs) between computing platforms engaged in (e.g., Internet-of-Things) data exchange via peer-to-peer (P2P) connections are described. In accordance with various embodiments, data traffic via the P2P connections is monitored, and if an SLA violation is detected, data streams are rerouted to cure the violation.

System and methods for enforcing service level agreements (SLAs) between computing platforms engaged in (e.g., Internet-of-Things) data exchange via peer-to-peer (P2P) connections are described. In accordance with various embodiments, data traffic via the P2P connections is monitored, and if an SLA violation is detected, data streams are rerouted to cure the violation.

Active-active standby is maintained for communication sessions using session initiation protocol (SIP) processes between two active session zones in a first datacenter and a standby session zone in a second datacenter. In the event of a failure at a first active session zone at the first datacenter, a failover to the second active session zone at the first datacenter is performed such that there are no interruptions in the active sessions. In the event of a failure at both active session zones at the first datacenter, a failover to the second datacenter is performed.

An example method includes receiving, from a customer system by a cloud exchange comprising processing circuitry, a request to communicatively couple a virtual gateway on network infrastructure of the cloud exchange to a network gateway communicatively coupled to a public network, the request including data indicating a public Internet Protocol (IP) address of the customer system, wherein the customer system is configured with a first connection communicatively coupling the customer system and the public network via a network service provider (NSP) that is separate from the cloud exchange; configuring, by the cloud exchange, a network route for a network gateway to the virtual gateway, the network gateway communicatively coupled to the public network; and providing, by the cloud exchange to the network gateway, routing information including the public IP address of the customer system to create a second connection communicatively coupling the customer system and the public network.