Systems, methods and/or computer program products managing momentary increases in resource requirements of microservices within a service mesh using sliced replicas or pre-configured cloud functions. The service mesh tracks incoming API calls of applications requesting use of specific microservice capabilities. Over time capabilities being called are categorized by the service mesh based on call frequency. Service mesh predicts patterns of expected increases in requests for each capability of the microservices. As the increase in the number of API calls for the capability become more than a threshold level predicted by the service mesh, a sliced replica of the microservice is created or a pre-configured cloud function is enabled to handle requests specifically for the capability causing the momentary increase in resource requirements, while the service mesh continues routing API calls for other capabilities to the requested microservice. Upon resource requirements subsiding, the sliced replica or pre-configured cloud function is removed.

Systems, methods and/or computer program products managing momentary increases in resource requirements of microservices within a service mesh using sliced replicas or pre-configured cloud functions. The service mesh tracks incoming API calls of applications requesting use of specific microservice capabilities. Over time capabilities being called are categorized by the service mesh based on call frequency. Service mesh predicts patterns of expected increases in requests for each capability of the microservices. As the increase in the number of API calls for the capability become more than a threshold level predicted by the service mesh, a sliced replica of the microservice is created or a pre-configured cloud function is enabled to handle requests specifically for the capability causing the momentary increase in resource requirements, while the service mesh continues routing API calls for other capabilities to the requested microservice. Upon resource requirements subsiding, the sliced replica or pre-configured cloud function is removed.

Systems and methods for cloud-based hybrid service meshes in microservice architectures are disclosed. A method for selection of a microservice in a cloud-based hybrid mesh microservice architecture may include: (1) receiving, at a hybrid service mesh library in a first microservice instance, a request for a second microservice, wherein the hybrid service mesh library comprises microservice information for a plurality of microservice instances comprising an identification of each microservice instance, a location for each microservice instance, and a status for each microservice instance; (2) identifying, by the hybrid service mesh library, a number of microservice instances for the microservice and the location of each microservice instance; (3) selecting, by the hybrid service mesh library, one of the plurality of microservice instances; and (4) calling, by the hybrid service mesh library, the selected microservice instance.

Systems and methods for cloud-based hybrid service meshes in microservice architectures are disclosed. A method for selection of a microservice in a cloud-based hybrid mesh microservice architecture may include: (1) receiving, at a hybrid service mesh library in a first microservice instance, a request for a second microservice, wherein the hybrid service mesh library comprises microservice information for a plurality of microservice instances comprising an identification of each microservice instance, a location for each microservice instance, and a status for each microservice instance; (2) identifying, by the hybrid service mesh library, a number of microservice instances for the microservice and the location of each microservice instance; (3) selecting, by the hybrid service mesh library, one of the plurality of microservice instances; and (4) calling, by the hybrid service mesh library, the selected microservice instance.

In one embodiment, a device detects oscillations in a path metric for a network path between violating a service level agreement for an online application and not violating the service level agreement for the online application. The device classifies the oscillations as near-boundary or wild, based on degrees to which the path metric violated a threshold of the service level agreement. The device provides data regarding the oscillations to a user interface that includes an indication as to whether the oscillations are near-boundary or wild. The device adjusts the threshold of the service level agreement based in part on feedback from the user interface, when the oscillations are near-boundary.

In one embodiment, a device detects oscillations in a path metric for a network path between violating a service level agreement for an online application and not violating the service level agreement for the online application. The device classifies the oscillations as near-boundary or wild, based on degrees to which the path metric violated a threshold of the service level agreement. The device provides data regarding the oscillations to a user interface that includes an indication as to whether the oscillations are near-boundary or wild. The device adjusts the threshold of the service level agreement based in part on feedback from the user interface, when the oscillations are near-boundary.

The present invention is directed to a system and a method for facilitating the consistent update of routing tables across the routers of a routing layer in a distributed messaging system. The routers are configured to send together with the outbound message the routing table version used to route the outbound message, which is compared, at the level of the enqueue layer, with the latest deployed routing table version and/or the latest routing table version used to route messages to the requested message queue. If the routing table version of the outbound message is older than the latest deployed routing table version and/or the latest routing table version used to route messages to the requested message queue, then the outbound message is rejected, otherwise, the message is enqueued to the requested message queue.

The present invention is directed to a system and a method for facilitating the consistent update of routing tables across the routers of a routing layer in a distributed messaging system. The routers are configured to send together with the outbound message the routing table version used to route the outbound message, which is compared, at the level of the enqueue layer, with the latest deployed routing table version and/or the latest routing table version used to route messages to the requested message queue. If the routing table version of the outbound message is older than the latest deployed routing table version and/or the latest routing table version used to route messages to the requested message queue, then the outbound message is rejected, otherwise, the message is enqueued to the requested message queue.

In a system including a plurality of computing subsystems executing a set of hosted applications, each of the computing subsystems maintains a copy of a common routing matrix defining, for each hosted application, an identifier of a computing subsystem configured to host the application. A first intra-subsystem routing component of a first one of the computing subsystems receives a message; determines a target one of the hosted applications to process the message; identifies, according to the common routing matrix, a second one of the computing subsystems that executes the target hosted application; and in response to the identifying, provides the message and a routing indicator to a first inter-subsystem routing component of the first computing subsystem. The first inter-subsystem routing component the transmits the message to the second computing subsystem.

Techniques for using global virtual network instance (VNI) labels in a multi-domain network to route network data with a multi-tenant network overlay are described herein. A routing device provisioned in a network domain of the multi-domain network may register with a service discovery system of the network domain for use of network configuration data to establish routes through the multi-domain network with network nodes. Each network domain of the multi-domain network may include an application programming interface (API) server for processing API requests to make changes to configurations of a network domain. A border gateway protocol (BGP) large community may be utilized to encode global VNI labels, network addresses, local next hop nodes, and/or additional network information and sent to routing devices provisioned in separate network domains. A service chain may be signaled by global VNI labels to route network traffic through various services prior to reaching a destination endpoint.