Described embodiments provide systems and methods for connecting to a server of a plurality of servers. The system may include a device intermediary between a client and a plurality of servers. The device may receive a remote desktop protocol (RDP) request from the client to connect to one of the plurality of servers. The RDP request may include a token. The device may cause a load-balancer of the plurality of servers to modify or remove the token of the RDP request, responsive to presence of a session directory/broker. The device may receive a server redirect packet that indicates a target server identified from the plurality of servers by the session directory, to which the client is to connect. The device may cause the server redirect packet to be modified to cause the client to send a redirected connection request packet for connecting with the target server.

Described embodiments provide systems and methods for connecting to a server of a plurality of servers. The system may include a device intermediary between a client and a plurality of servers. The device may receive a remote desktop protocol (RDP) request from the client to connect to one of the plurality of servers. The RDP request may include a token. The device may cause a load-balancer of the plurality of servers to modify or remove the token of the RDP request, responsive to presence of a session directory/broker. The device may receive a server redirect packet that indicates a target server identified from the plurality of servers by the session directory, to which the client is to connect. The device may cause the server redirect packet to be modified to cause the client to send a redirected connection request packet for connecting with the target server.

A computing system may evaluate contents of a file to determine at least one user identifier for at least one suggested recipient of the file. The computing system may receive an input from a client device that indicates the file is to be shared, and in response to the input, the computing system may send the at least one user identifier to the client device.

One or more computing devices, systems, and/or methods for implementing a publish and subscribe communication system utilizing a load balancer and task schedulers are provided. Subscription requests are received from subscribers for subscribing to a topic published by a publisher. An external subscription list is maintained to track communication address information of the subscribers. A number of task schedulers are created based upon a count of subscribers within the external subscription list. The subscribers are assigned to the task schedulers such that a number of subscribers assigned to a task scheduler is limited according to a subscriber assignment limit. In response to the publisher creating data to publish to the topic, the task schedulers are controlled to use the communication address information to directly transfer data of the topic to the subscribers assigned to the task schedulers.

A method for managing systems with interrelated microservices with self-assembling and self-configuring microservices includes receiving at a first micro service a service request from a client. A determination is the made whether the first micro service is capable of processing the service request. If the first micro service is capable of processing the service requests, then processing the service request; if the first micro service cannot process the service request then routing the service request to a first stem service. The first stem service determines whether there is a second micro service that can process the service request. If the second micro service that can process the service requests exists, then forwarding the service request to the second micro service for processing. If there is no second micro service that can service the service requests then morphing the first stem service into a micro service that can service the service request.

A method for managing systems with interrelated microservices with self-assembling and self-configuring microservices includes receiving at a first micro service a service request from a client. A determination is the made whether the first micro service is capable of processing the service request. If the first micro service is capable of processing the service requests, then processing the service request; if the first micro service cannot process the service request then routing the service request to a first stem service. The first stem service determines whether there is a second micro service that can process the service request. If the second micro service that can process the service requests exists, then forwarding the service request to the second micro service for processing. If there is no second micro service that can service the service requests then morphing the first stem service into a micro service that can service the service request.

Exemplary methods, apparatuses, and systems include a path management hub and proxy server nodes that form a mesh network. The hub receives link performance metrics from each of the nodes. The hub determines optimal paths between first and second nodes for each of a plurality of metric types or a combination of metric types using the received link performance metrics. The hub maps a service identifier to a plurality of the determined optimal paths for a context representing one or more link performance metric types. The hub transmits a next hop for each of the plurality of mapped optimal paths along with the mapping to the first node. The first node receives the service identifier mapped to the next hops and traffic for the first connection. In response to determining the received traffic is for the service, the first node selects a first next hop and forwards the traffic.

Exemplary methods, apparatuses, and systems include a path management hub and proxy server nodes that form a mesh network. The hub receives link performance metrics from each of the nodes. The hub determines optimal paths between first and second nodes for each of a plurality of metric types or a combination of metric types using the received link performance metrics. The hub maps a service identifier to a plurality of the determined optimal paths for a context representing one or more link performance metric types. The hub transmits a next hop for each of the plurality of mapped optimal paths along with the mapping to the first node. The first node receives the service identifier mapped to the next hops and traffic for the first connection. In response to determining the received traffic is for the service, the first node selects a first next hop and forwards the traffic.

Cascading payload replication to target compute nodes is disclosed. Cascading payload replication can be accomplished using a two-stage operation for a replication operation. In the first stage, a plan is generated and distributed for the replication operation. The plan includes an assignment of compute nodes to tree nodes in a tree hierarchy. In the second phase, the payload is distributed according to the plan. The plan is different for at least two replication operations. Thus, the cascading payload replication is adaptable to changing target compute nodes and provides for load balancing.

Various embodiments of apparatuses and methods for transaction processing at edge servers in a content distribution network (“CDN”) are described. In some embodiments, an edge server receives an initial request from a client for content associated with a particular origin, and then provides the content to the client. The edge server can then receive another request from the client that might include an indicator for transaction processing. The edge server determines that transaction processing is indicated for handling this new request, in some embodiments. The edge server can then send a transaction notification to the origin, receive a transaction continuation response from the origin, and then execute a data transaction with transaction entities that are distinct from the content distribution network and the origin, in some embodiments. If the transaction is successful, the edge server can notify the client and the origin of the successful transaction, in some embodiments.