Patent classifications
H04L67/1031
TECHNIQUES FOR UTILIZING DIRECTED ACYCLIC GRAPHS FOR DEPLOYMENT INSTRUCTIONS
Techniques are disclosed for utilizing directed acyclic graphs for deployment instructions. A computer-implemented method can include various operations. Instructions may be executed by a computing device to perform parses of configuration data associated with a deployment. The computing device may cause a first directed acyclic graph (DAG) to be generated, the first DAG being utilized for deploying a first resource based on the parses. A second DAG may be generated for deploying execution targets based on the parses, the second DAG specifying dependencies between execution targets of the deployment. The computing device may generate a linked list data structure based on the parses and may deploy the computing system by traversal of the linked list data structure.
SYSTEM AND METHOD FOR PRIORITIZING TENANTS FOR A SERVICE FOR A REQUEST ROUTER IN A CLOUD-BASED SOFTWARE AS A SERVICE (SAAS) PLATFORM CONTACT-CENTER
A computerized-method for service monitoring and rate limiting for a service for a request router in a SaaS-platform-contact-center is provided herein. When a service-monitoring-module for a microservice of the SaaS-platform-contact-center is operating and a request-router is in a throttle-mode for a service-of-the-microservice, operating a Tenants Prioritization (TP) module. The TP module includes: determining a tenant-tier-level having a determined quota-of-service-requests; receiving a degradation-level from the service-monitoring-module, for a preconfigured-period; reducing corresponding predefined total-number-of-allowed-requests by a first-threshold, when the degradation-level of the service-of-the-microservice has degraded by a second-threshold, during the preconfigured-period; increasing the corresponding predefined total-number-of-allowed-requests by the first-threshold, when the degradation-level of the service-of-the-microservice has improved by the second-threshold, during the preconfigured period; and instructing the request-router to get out of throttle-mode for the service-of-the-microservice, when the degradation-level of the service-of-the-microservice has improved by the second-threshold during the preconfigured period and there is an indication that the service-of-the-microservice has been degraded.
CLUSTER INSTANCE BALANCING OF A DATABASE SYSTEM ACROSS ZONES
The subject technology selects a particular zone among multiple zones based on a target skew to meet a global balancing of cluster instances. The subject technology deploys a particular type of cluster instance to the particular zone. The subject technology, for each zone from the multiple zones, determines a respective number of cluster instances. The subject technology identifies a second particular type of cluster instance to remove based on a total number of the second particular type of cluster instance in the multiple zones and a second total number of the particular type of cluster instance in the multiple zones. The subject technology removes the second particular type of cluster instance from a second particular zone to meet the global balancing of cluster instances in the multiple zones.
DYNAMIC LOAD BALANCING IN REACTIVE SYSTEMS
A computer system hosting (micro)services that uses a service mesh to govern communication between the services. The services include consumer services and an event stream service, the latter directing an event stream from a producer service to the individual consumer services. The control plane of the service mesh has the role of creating and removing service instances. Based on a specified event capacity that is to be provided by the consumer services collectively, the control plane manages service provisioning by estimating the current event capacity of the system. This is done by measuring the event capacities of each consumer service instance and summing them, from which any shortfall or excess of the current event capacity in relation to the specified event capacity can be determined. Consumer service instances are then added in case of a shortfall or removed in case of an excess as needed to avoid over or under-provisioning.
ORCHESTRATED RECONNECT FOR CLIENT-UNAWARE ROLLING OF NETWORK NODES
Techniques for the transparent rolling of nodes in a cloud-delivered headend service without disrupting client traffic or making users aware of the various nodes in the system being rolled are described herein. The techniques may include receiving an indication that a first node of a network is to be rolled. Based at least in part on the indication, new connection requests may not be sent to the first intermediate node. Additionally, a client device having an existing connection through the first node may be identified. In some examples, a request may be sent to the client device to prompt the client device to establish a new connection. After determining that the new connection has been established such that the new connection flows through a second node of the network, the first node may be rolled.
DYNAMIC ALLOCATION AND USE OF IMS PROCESSING RESOURCES
According to the present disclosure various network functions are dynamically instantiated on a selected data center to utilize the most efficient and rapid resources available. An analytic module and a data lake receive performance data from the various data centers of a cellular network, such as a Regional Data Center, a National Data Center and an Edge Data Center. The analytic module will analyze the received performance data and apply artificial intelligence and machine learning to determine current resource use and estimate future resources available on various data centers of the cellular network. The appropriate data center is then selected to perform a particular network function.
Dynamic overflow processing in a multi-user computing environment
Dynamic overflow processing is provided in a multi-user computing environment, which includes receiving, from a user, a request for a new user session at a port of a process of the multi-user computing environment, where the process supports multiple users via the port, and determining that accommodating the new user session will result in resource usage of the process exceeding a predetermined capacity threshold for the process. Based on determining that capacity threshold will be exceeded, the process redirects the request for the new user session to an overflow process started by the process, where the overflow process is an additional instance of the process running within the multi-user computing environment. The process receives a response from the overflow process to the request for the new user session, and forwards the received response to the request for the new user session to the user.
Management device, storage system, and information processing method
A management device of a storage system, the management devices includes a memory and a processor. The processor coupled to the memory and configured to acquire workload load information and system load information when executing a container, and determine a workload arrangement destination and a replica position of a volume based on the workload load information and the system load information when activating a workload.
Management device, storage system, and information processing method
A management device of a storage system, the management devices includes a memory and a processor. The processor coupled to the memory and configured to acquire workload load information and system load information when executing a container, and determine a workload arrangement destination and a replica position of a volume based on the workload load information and the system load information when activating a workload.
Scaling of services in a distributed system
Embodiments for scaling services in a distributed network by registering bucket names for the services with a Domain Name Service (DNS) server. Buckets hold resources and distribution of buckets to servers is maintained using a Consistent Hashing Ring. Upon determining that services servers need to be added or deleted based on changes load conditions, leave/join events are managed by a Kubernetes event service and updates are propagated to all of the services by the membership service component. A service scaling process updates the mapping of buckets to the host name of the new service server. A resource request from a client is sent to the mapped bucket name, and a DNS resolver process sends it to the changed service server so that the client is completely unaware of this change in bucket ownership.