Examples provide a permission service for controlling service requests to web services. A permission controller monitors the number of active requests to a selected web service. When a permission request associated with the selected web service is received from a client, the permission service compares the current number of active requests to a per-service maximum threshold number of active requests. The permission controller maintains a per-threshold number of active requests customized for each web service. If the current request would exceed the threshold number if granted, the permission controller sends a denial with a random wait time to the client. The client resends the permission request on expiration of the wait time. The permission controller generates a different random wait time for each denial response. If the number of active requests is less than or equal to the threshold, the permission service grants permission to the client.

Embodiments include a multi-tenant cloud system with a first data center and a second remote data center. The first data center authenticates a first client and stores resources that correspond to the first client, and is in communication with the second data center. The second data center authenticates the first client and replicates the resources. The first data center receives a write request for the first client, writes the write request and generates change event messages in a first order. The first data center pushes the change event messages to the second data center via REST API calls. In response to receiving the change event messages, the second data center is configured to write the change event messages in the first order to its local database.

A server of an on-premises data center used for a software platform identifies a condition impacting real-time communication services at a premises housing devices accessing the software platform. The server transmits, to a device of an administrator associated with the premises via a messaging application for real-time communication between two or more human-operated devices, a message indicating the condition and including one or more selectable elements each associated with a different action for addressing the condition. The server receives an indication of a selectable element selected from amongst the one or more selectable elements at the device of the administrator. The server causes performance of the action associated with the selected selectable element.

In some examples, a system generates an identifier for association with a user financial account. The identifier may have a syntax including a currency indicator and a string including one or more characters concatenated together such that the currency indicator appears immediately before the string. The system generates a user-defined identifier and maps, in a database, the user-defined identifier to the user financial account. The system receives a message indicating an intent to transfer funds from a sending user to a receiving user. The message may include the user-defined identifier in lieu of account information of the user financial account, to identify the user as the receiving user. The system parses the message to identify the user-defined identifier and accesses the account information of the user financial account using the identifier. The system initiates a transfer of funds from the sending user account to the user financial account.

Embodiments operate a multi-tenant cloud system. At a first data center, embodiments authenticate a first client corresponding to a first tenant ID and store resources that correspond to the first client, the first data center in communication with a second data center that is configured to authenticate the first client and replicate the resources. The first data center receives an Application Programming Interface (“API”) request for the first client corresponding to a change to the resources, and generates a change log and corresponding change event message in response to the API request. Embodiments compute a first hash corresponding to the first tenant ID of the change log to determine a first partition of a first queue at the first data center. The first data center pushes the change event message to the second data center via an API call.

Embodiments operate a multi-tenant cloud system. At a first data center, embodiments authenticate a first client corresponding to a first tenant ID and store resources that correspond to the first client, the first data center in communication with a second data center that is configured to authenticate the first client and replicate the resources. The first data center receives an Application Programming Interface (“API”) request for the first client corresponding to a change to the resources, and generates a change log and corresponding change event message in response to the API request. Embodiments compute a first hash corresponding to the first tenant ID of the change log to determine a first partition of a first queue at the first data center. The first data center pushes the change event message to the second data center via an API call.

An apparatus comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: manage an application service using a management web portal; request, using the management web portal, the application service with a given service level agreement from a catalogue of offered application services; and communicate, using the management web portal, with an application service management function; wherein the application service management function is configured to translate the service level agreement of the requested application service to a specification of an application slice, and to trigger a creation of an application slice instance by contacting an application slice management function.

In some examples, a payment system generates, for a first user, a proxy identifier having a syntax including a symbol and a string of one or more characters that are concatenated such that the symbol appears immediately before the string. The proxy identifier is associated with a financial account of the first user. The payment system receives an indication of an intent to transfer funds from a second user to the first user. The indication includes the proxy identifier in lieu of financial account information of the first user, and to identify the financial account of the first user for receiving the funds. Based at least on identifying the proxy identifier, the payment system accesses the financial account information of the first user and initiates the transfer of funds from the financial account of the second user to the financial account of the first user.

Systems and methods for associating sessions of encrypted identifiers are provided. A collection of data packets received during one or more sessions within a time period may be retrieved. Each packet in the collection may be associated with a unique identifier of a respective session. An epoch time may be calculated for each of the retrieved data packets based on the determined skew and respective timestamp information of the data packet. It may be identified as to whether each of the calculated epoch times matches a previously calculated epoch time for a packet associated with a previous session or a session that has previously been associated with a selected session. The timestamp information may be associated with a browser identifier and subject to encryption/decryption by an identifier server or authorized parties.

This application provides a trace chain information query method, including: receiving, by a trace chain server, first trace chain information sent by a first service node and second trace chain information sent by a second service node, where the first service node is a service node in a first trace chain, the second service node is a service node in a second trace chain, both the first trace chain and the second trace chain are generated as triggered by a same user operation, the first trace chain information includes a group identifier, the second trace chain information includes the group identifier, and the group identifier is used to indicate the user operation; and finding, by the trace chain server, the first trace chain information and the second trace chain information based on the group identifier.