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.

A method includes creating a publisher configured to send messages over a channel having a shared memory. The method includes creating at least one subscriber configured to receive the messages over the channel by sequentially referencing memory slots of the plurality of memory slots. The method includes determining that the next sequential memory slot is currently referenced by a subscriber. The method includes delaying sending the message by the publisher based on determining that the next sequential memory slot is currently referenced by the subscriber. The method includes receiving an event trigger indicative of message reading by the subscriber. The method includes, responsive to receiving the event trigger, determining that the next sequential memory slot is not currently referenced. The method includes sending the message to the next sequential memory slot based on determining that the next sequential memory slot is not currently referenced.

A system and a method for processing a message on a processing platform, such as a Kafka processing platform, are provided. The method includes: acquiring a plurality of partitions from the messaging platform; designating a first partition from among the plurality of partitions as a sticky partition; generating a plurality of routing keys that are configured to route messages to the sticky partition; using a first routing key from among the plurality of routing keys to identify a first service subscription; subscribing to a second service using the first routing key; and receiving a message transmitted by the second service.

An embodiment of the present disclosure includes an RPC architecture that includes a central manager gateway with a client-facing side that allows for client access via web services protocols such as SOAP and REST. The central manager gateway further includes a server-facing side that can communicate with a plurality of network elements, with each network element implementing a common IDL architecture and RPC manager instance. Each of the network elements, and in particular their RPC manager instance, may communicate with other RPC manager instances to ‘learn’ the network topology for the system and maintain a topology database for purposes of exposing a naming service, e.g., a CORBA naming service. The network elements may elect one master element while the others remain as slaves. The central manager gateway may automatically locate the master network element and forward client requests to the same for servicing.

Some embodiments provide a program. The 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 comprising 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.

The described technology relates to a publish-subscribe message framework in which an application, decomposed to a plurality of processing stages, is run by executing respective processing stages of the application asynchronously and simultaneously with each other. Communications between the respective processing stages may exclusively be in accordance with the publish-subscribe execution model. The described publish-sub scribe framework provides for processing stages to be executed in a multi-process and/or multi-threaded manner while also enabling the distribution of the processing stages to respective processing resources in a multi-processor/multi-core processing environment. An example electronic exchange application and a corresponding example exchange gateway application are described.

Systems and methods described herein provide for management of notifications. A computing device in communication with a client device receives a notification from at least one notification source. The notification may be for rendering on a screen at the client device. A policy engine of the computing device may identify a context of the notification. The policy engine may add a tag to the notification according to the identified context to control rendering of the notification at the client device. The computing device may transmit the notification with the tag to a notification service at the client device. The notification service may be configured to manage the notification at the client device in accordance with the tag.

A system is described to manage a plurality of managed devices. The system may have an Application Program Interface (API), a messaging platform, an application manager, and a payments manager. The Application Program Interface (API) may be configured to communicate with a user computer to request use of one or more of the managed devices. The messaging platform may be configured to send and receive messages to the managed devices. The messaging platform operates using a publish/subscribe protocol and the messages control installation of applications requested by the user computer, and allow communications between managed devices based on topics. The application manager, in communication with the messaging platform, deploys applications on the managed devices. The payments manager processes payment for the use of the one or more managed devices.

Systems and methods are described for preprocessing data later ingested into an indexing system. The preprocessing can include receiving messages published to a first publish-subscribe messaging system, the messages containing raw machine data generated by one or more components in an information technology environment, performing one or more processing operations on at least some of the messages to generate preprocessed messages, republishing the preprocessed messages to a second publish-subscribe messaging system, and providing to the indexing system, a subset of the messages from the second publish-subscribe messaging system.

A computer implemented method implemented on an allocation computing unit for distributing a pre-defined workflow comprising a nonempty set of workflow components, the workflow components being ordered in a directed acyclic precedence graph, onto a set of general purpose computing units comprising at least two general purpose computing units.