Abstract: Aspects of the disclosure relate to order processing. A computing platform may determine that order processing for a subset of a plurality of trading pairs should be migrated from a source computing platform to a destination computing platform. The destination computing platform may configure itself to process first trading pair, and may enter a proxy mode where orders for the subset of the plurality of trading pairs are routed to the destination computing platform. The destination computing platform may receive and load order processing information corresponding to the subset of the plurality of trading pairs, and may direct the source computing platform to cease processing for the subset of the plurality of trading pairs. The destination computing platform may disable the proxy for the source computing platform, and may receive orders/process for the subset of the plurality of trading pairs.

Abstract: Aspects of the disclosure relate to order processing. A computing platform may determine that order processing for a subset of a plurality of trading pairs should be migrated from a source computing platform to a destination computing platform. The destination computing platform may configure itself to process first trading pair, and may enter a proxy mode where orders for the subset of the plurality of trading pairs are routed to the destination computing platform. The destination computing platform may receive and load order processing information corresponding to the subset of the plurality of trading pairs, and may direct the source computing platform to cease processing for the subset of the plurality of trading pairs. The destination computing platform may disable the proxy for the source computing platform, and may receive orders/process for the subset of the plurality of trading pairs.

Abstract: An approach is disclosed for metering usage of cloud computing services at a feature level. In one embodiment, a metering application receives feature status information indicating which features of a cloud computing service are enabled through an event-driven process, in which events are generated and reported to the metering application when features are enabled or disabled, as well as a polling process, in which the metering application periodically queries the statuses of features. Feature status information gathered by the metering application is persisted in a database as collective feature statuses, with each collective feature status being associated with an interval of time during which feature statuses are unchanged. The feature status information obtained and persisted in the database may then be used to, for example, determine licensing fees based on feature usage or report feature usage to facilitate quantitative studies of the usefulness of features.

Abstract: Techniques disclosed herein provide a messaging protocol for a distributed system. In one embodiment, each message constructed according to the messaging protocol includes a field for a list of globally unique identifiers (GUIDs) of nodes that should not reply to the message. A new node joining the system sends a message requesting system state information and including an empty GUID list, indicating that all nodes receiving the message should reply. In normal operation, the system's state information is synchronized among all nodes at regular intervals by exchanging messages indicating local state changes at each node, and including GUID list fields specifying all other nodes' GUIDs so that no nodes reply. A node which identifies messages that should have been received from another node but are missing transmits a message requesting the missing messages, with a GUID list including all nodes other than the other node that sent the missing messages.

Abstract: An approach is disclosed for metering usage of cloud computing services at a feature level. In one embodiment, a metering application receives feature status information indicating which features of a cloud computing service are enabled through an event-driven process, in which events are generated and reported to the metering application when features are enabled or disabled, as well as a polling process, in which the metering application periodically queries the statuses of features. Feature status information gathered by the metering application is persisted in a database as collective feature statuses, with each collective feature status being associated with an interval of time during which feature statuses are unchanged. The feature status information obtained and persisted in the database may then be used to, for example, determine licensing fees based on feature usage or report feature usage to facilitate quantitative studies of the usefulness of features.

Abstract: Techniques disclosed herein provide a messaging protocol for a distributed system. In one embodiment, each message constructed according to the messaging protocol includes a field for a list of globally unique identifiers (GUIDs) of nodes that should not reply to the message. A new node joining the system sends a message requesting system state information and including an empty GUID list, indicating that all nodes receiving the message should reply. In normal operation, the system's state information is synchronized among all nodes at regular intervals by exchanging messages indicating local state changes at each node, and including GUID list fields specifying all other nodes' GUIDs so that no nodes reply. A node which identifies messages that should have been received from another node but are missing transmits a message requesting the missing messages, with a GUID list including all nodes other than the other node that sent the missing messages.