G06F2209/547

Streaming traffic pattern for public cloud auto scaling

A total number of messages in a set of messages that are processed by a computing node in a virtual computer cluster during a time interval is determined. The virtual computer cluster is deployed with a cloud computing service and includes the computing node and other computing nodes at an end time of the time interval. It is determined whether the total number of messages in the set of messages processed by the computing node is no less than a maximum per-interval message number threshold. In response to determining that the total number of messages is no less than a maximum per-interval message number threshold, the cloud computing service is caused to start an additional computing node in the virtual computer cluster after the time interval, wherein the additional computing node is used to process one or more subsequent messages to be processed after the time interval.

Event-level granular control in an event bus using event-level policies

A message-level policy implemented with for a message routing system may be used to mediate between a variety of message sources and message targets that receive and use messages. The message-level policy may allow fine grained message-by-message policy assessment that a message routing system policy may be able to provide. The message-level policy may furthermore interact with the message routing system policy to provide mechanisms to avoid accidental leakage of protected messages or spill-over to protected regions.

A REST INTERFACE SPECIFICATION ENCAPSULATION SYSTEM BASED ON NETWORK SNIFFING
20230305907 · 2023-09-28 ·

The present invention discloses a REST interface specification encapsulation system based on network sniffing, comprising: an API traffic sniffing module, an API specification extraction module and an API sharing platform module. The API traffic sniffing module realizes the interception and analysis of the API call traffic in mobile applications based on the principle of Man-in-the-Middle Attack. The API specification extraction module is responsible for filtering and classifying the intercepted API call collection, and automatically generating the API specification in JSON HyperSchema format. The API sharing platform module implements sharing, openness and display of the API specification with JSON HYPERSCHEMA as the core, and provides sharing permission control, search, API call test, and API specification error correction function. the REST interface specification encapsulation system improves the efficiency and accuracy of API specification extraction, and the encapsulation system is versatility and practical.

Method and system for providing resiliency in interaction servicing across data centers

A system and a method for providing resiliency in a telephony communication system are provided. The method includes: obtaining resources that are available in a first data center; receiving, from a client, a request for accessing a first resource; transmitting, to the client, a first Uniform Resource Locator (URL) that includes information for facilitating a client access to the first resource in the first data center; when the first resource becomes unavailable in the first data center and available in a second data center, transmitting, to the second data center, a subscribe message for facilitating a client access to the first resource in the second data center; and when the client access to the first resource in the second data center is available, transmitting, to the client, a second URL that includes information for facilitating the client access to the first resource in the second data center.

TEMPLATE DRIVEN APPROACH TO DEPLOY A MULTI-SEGMENTED APPLICATION IN AN SDDC

Some embodiments provide a simplified mechanism to deploy and control a multi-segmented application by using application-based manifests that express how application segments of the multi-segment application are to be defined or modified, and how the communication profiles between these segments. In some embodiments, these manifests are application specific. Also, in some embodiments, deployment managers in a software defined datacenter (SDDC) provide these manifests as templates to administrators, who can use these templates to express their intent when they are deploying multi-segment applications in the datacenter. Application-based manifests can also be used to control previously deployed multi-segmented applications in the SDDC. Using such manifests would enable the administrators to be able to manage fine grained micro-segmentation rules based on endpoint and network attributes.

Processing state changes to applications

A program receives a state change that occurred for an event created by an application. The event includes a creator of the event, a set of objects, and a set of sources. The program further identifies a schema definition in a plurality of schema definitions based on a type of the state change that occurred for the event. Each scheme definition in the plurality of schema definitions specifies a type of state change and a set of information associated with the event. The program also generates a message that includes the set of information associated with the event specified in the identified schema definition and a set of targets. The program further sends the message to a message management platform in order for the message management platform to send to an application for presentation to each target in the set of targets through a web portal provided by the application.

Inter-ledger messaging in a blockchain

Operating conditions of a blockchain configuration may be dynamic and change automatically under certain circumstances. One example method of operation may include receiving a blockchain transaction sent from a first blockchain to a second blockchain, identifying an inter-ledger contract between the first blockchain and the second blockchain, receiving an inter-ledger message at the second blockchain from the first blockchain, and determining whether to log the blockchain transaction in the first blockchain or the second blockchain based on the inter-ledger message.

SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT FOR SHARING INFORMATION IN A DISTRIBUTED FRAMEWORK
20210357276 · 2021-11-18 ·

A system, method and computer program product are provided for receiving information associated with a message, issuing a storage resource request in connection with a storage resource and determining whether the storage resource is available. In use, the information is capable of being shared in less than one second, utilizing an automotive electronic control unit which includes a plurality of interfaces.

Messaging in a multi-cloud computing environment
11175970 · 2021-11-16 · ·

A method for messaging in a hybrid multi-cloud computing environment may include receiving, from a multi-cloud controller, a message. The hybrid multi-cloud computing environment may include multiple cloud platforms hosted on private, on premise infrastructure as well as public, third-party infrastructure. The multi-cloud controller may send the message to control an operation of the cloud platform. In response to receiving the message from the multi-cloud controller, the message may be deposited in message queue. The cloud platform may send a request to retrieve data destined for the cloud platform. The message from the message queue may be sent to the cloud platform in response to the request. Related systems and articles of manufacture, including computer program products, are also provided.

Hierarchical scheduler

Methods, systems, and computer programs are directed to the implementation of configurable hierarchical schedulers with multiple levels, where each level may use one of several types of queueing mechanisms. A configurable, hierarchical scheduler is designed to handle large scale processing of requests (e.g., transmitting outgoing messages). The hierarchical scheduler distributes the loads to different queues handling different types of messages (e.g., by user ID, by Internet Address (IP), by schedule). The different layers of the hierarchical scheduler are configurable to queue and schedule traffic based on many factors, such as IP address, handling reputation, available downstream bandwidth, fairness, concurrency rates to handle multiple constraints, scheduling per client, time of delivery constrains, rate limits per user, domain scheduling per user, concurrency throttling per outbound channel, and sharing global rate limits across service processors.