Described herein are systems and methods for end user connection load balancing amongst multiple on-premise connector proxies deployed across geographic locations and reducing connection setup latency without using a shared or distributed database. The system can load balance connections deterministically amongst the on-premise connector proxies using load statistics. The system utilizes an intelligent DNS service that can use network experience data, service availability, and application metrics to provide sophisticated traffic management via DNS or API-based decisions. The system can include a domain name system (DNS) resolver configured to receive metrics for a first connector and a second connector of a data center of an entity, receive a DNS request including an entity identifier and a data center identifier; and transmit a response to the DNS request identifying a server selected based on the metrics identified using the entity identifier and the data center identifier.

Methods, systems, and processes to simplify networking setup complexity for security agents implemented in cybersecurity computer environments are disclosed. A request with an intentionally bad Transport Layer Security (TLS) handshake is transmitted from an agent to a server. An indication is received from the server that the request has been rejected. A Round Trip Time (RTT) of the request and rejection of the request is determined. The server is then pinged based on the RTT. The subsequent pinging does not require whitelisting of an additional port and does not negatively interact with network intermediaries that support protocol detection.

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, computer program products, and methods are described herein for implementing hybrid cloud computation engines using infrastructure optimization. The present invention may be configured to identify, from a group of available infrastructures, an infrastructure to perform a computing request, where the group of available infrastructures includes an enterprise infrastructure and one or more cloud provider infrastructures. The present invention may be further configured to provide, to the identified infrastructure and via a blockchain distributed ledger, the computing request and input data for the computing request, where the computing request includes a request to generate, using a recurrent neural network, based on data in the blockchain distributed ledger, and based on the input data, output data. The present invention may be further configured to receive, from the identified infrastructure and via the blockchain distributed ledger, the output data.

Systems, computer program products, and methods are described herein for implementing hybrid cloud computation engines using infrastructure optimization. The present invention may be configured to identify, from a group of available infrastructures, an infrastructure to perform a computing request, where the group of available infrastructures includes an enterprise infrastructure and one or more cloud provider infrastructures. The present invention may be further configured to provide, to the identified infrastructure and via a blockchain distributed ledger, the computing request and input data for the computing request, where the computing request includes a request to generate, using a recurrent neural network, based on data in the blockchain distributed ledger, and based on the input data, output data. The present invention may be further configured to receive, from the identified infrastructure and via the blockchain distributed ledger, the output data.

An apparatus for constructing a cloud system may interpret a drawing file, may generate automation task information, which is the contents of an automation task including at least one of a task indicating that one or more cloud resources need to be automatically generated, modified or deleted, and a task indicating that software needs to be automatically installed, updated or deleted with respect to the one or more cloud resources, using the results of the interpretation, may interpret the automation task information, and may generate interface task information, which is the contents of an interface task for instructing a specific cloud platform or the specific one or more cloud resources to perform the automation task, using results of the interpretation.

An apparatus for constructing a cloud system may interpret a drawing file, may generate automation task information, which is the contents of an automation task including at least one of a task indicating that one or more cloud resources need to be automatically generated, modified or deleted, and a task indicating that software needs to be automatically installed, updated or deleted with respect to the one or more cloud resources, using the results of the interpretation, may interpret the automation task information, and may generate interface task information, which is the contents of an interface task for instructing a specific cloud platform or the specific one or more cloud resources to perform the automation task, using results of the interpretation.

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 circuitry 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.

Methods and systems for balancing online stores across servers. Monitoring a level of customer activity associated with a particular online store in a plurality of online stores. Detecting, based on the level of customer activity, a demand-level condition for the particular online store. Responsive to the detecting of the demand-level condition for the particular online store, moving one or more of the plurality of online stores from a first server of a plurality of servers to a second server of the plurality of servers.

Described herein are systems and methods for application health based network traffic routing in a geographically distributed cloud service. The domain name system (DNS) resolver can receive, from a service executing on one or more servers hosting a resource, a performance score of the resource. The performance score can be computed from a plurality of metrics determined from a performance monitoring service executing on the one or more servers in communication with the resource. The plurality of metrics can include a first set of performance metrics based on simulated client requests and a second set of performance metrics based on an application's own performance factors. The DNS resolver can receive, from a client, a request to resolve a DNS request. The DNS resolver can transmit, by the DNS resolver, a response to the request identifying the one or more servers selected based on the performance score of the resource.