Microsoft Technology Licensing, LLC

Visa International Service Association

Anurag Gupta

Lu Xun

Mihail Gavril Tarta

Gopal Krishna R Kakivaya

Richa Singh

Mert Coskun

Sumukh Shivaprakash

Jagadeesh Saravanan

Muralidhar Krishnaprasad

Balan Sethu Raman

Hua-Jun Zeng

Yang Li

Sameet Harishanker Agarwal

Anil Kumar Nori

Michael W Thomas

Rodger N Kline

Sanjay Anand

Maxim Mazeev

Srinivasmurthy P Acharya

Pehkeong Teh

Manoj K Valiyaparambil

Gopal Kakivaya

Sambavi Muthukrishnan

Vipul A Modi

Matthew Snider

Amit Shukla

Alex Wun

Mahadevan Venkatraman

Salome Jacob

Elsi Godolja

Sebastian Amara

Joseph Trdinich

Sameet H Argawal

Roopali Kaujalgi

Described are a system, method, and computer program product for real-time payment gateway event monitoring. The method includes receiving input data from a merchant system including an application URL associated with a merchant control interface having a web socket programmed and/or configured to persistently listen for HTTP POST messages, and an event of a payment gateway system. The method also includes monitoring ongoing events of the payment gateway system associated with ongoing transaction messages communicated from point-of-sale (POS) devices to the payment gateway system and detecting the event in the ongoing events. The method further includes, in response to detection of the event, generating a HTTP POST message including event data of the event, and communicating the HTTP POST message to the application URL to cause the merchant control interface to display the event data in a chart for visual representation of the event data.

System, method, and computer program product for real-time payment gateway event monitoring

A transactional replicator applying group commit and barrier concepts is disclosed. Group commit means that the transactional replicator commits multiple transactions in a group and is not restricted to committing single transactions one-at-a-time and is not limited to operating on a single state provider. Barrier means that the transactional replicator does not move forward to commit additional transactions until the previous group of transactions are completed. All state providers must apply their transactions and update state before additional transactions will be committed. A quorum acknowledgement 'unlocks' any locks that were acquired to update the state within a state provider. However, as long as there are no lock conflicts, additional transactions can continue to create new group commits as necessary.

Transactional replicator

Several API specification files that each include references to code elements that are defined within separate definitions and resources files may be merged together into a single specification for the new API. In this way, specifications for shared code elements that are common across the several specification files may be created without rewriting these specifications each time they are used in an API. A specification merging tool may look for a common reference in the API, match that reference to a definition or resource from the respective definition or resource document, and add that definition or resource to a merged specification file.

System and method for merging specification files for an application programming interface

In various implementations, methods and systems resource balancing in a distributed computing environment are provided. A client defined resource metric is received that represents a resource of nodes of the cloud computing platform. A placement plan for job instances of service applications is generated. The placement plan includes one or more movements that are executable to achieve a target placement of the job instances on the nodes. It is determined that the placement plan complies with placement rules. Each placement rule dictates whether a given job instance of the job instances is suitable for placement on a given node of the nodes. The placement plan is executed based on determining that the target placement of the job instances improves balance of resources across the nodes of the cloud computing platform based on the resource represented by the client defined resource metric.

Balancing resources in distributed computing environments

Embodiments are directed to managing multiple different types of applications using service groups. In one scenario, a computer system receives an indication of one or more application dependencies and characteristics that are to be implemented when an application is provisioned on a distributed host computer system. The computer system creates an application manifest that declaratively defines application dependencies and characteristics for various different service groups. Each service group includes applications that match the declaratively defined application dependencies and characteristics. The computer system also sends the manifest to the distributed host computer system which loads those applications that fit the manifest criteria onto available nodes of the distributed host computer system according to the service groups specified in the manifest.

Distributed application optimization using service groups

Embodiments are directed to ensuring that only one version of an application is running on a cluster. In one scenario, a computer system includes a configuration agent that generates service instance version queries upon startup to determine which service instance version to activate, maintains a service instance version table that includes a listing of service instance versions currently running on the computer system as part of one or more application instances and activates specified service instances. The computer system also includes a failover manager that manages service instance version queries. The failover manager indicates which service instance version to activate to ensure that the appropriate, current version is activated for each service instance. The computer system further includes a cluster manager that creates, deletes and upgrades service instances as part of an application instance upgrade.

Application version gatekeeping during upgrade

Systems and methods that supply a replication layer/agent that is generic to supporting a plurality of storage configuration as part of a distributed store. Such distributed store employs a Common Availability Substrate (CAS) for data transport and consistency, to render the distributed store scalable and available. Such an arrangement enables continuous operation of the store, while the replication subsystem creates new replicas (e.g., for load balancing, failover, and the like).

Replication for common availability substrate

An XML based type-definition language for declaring content-index for WinFS Types is provided. Content-index declarations can be specified for the Item type as well as it's sub-entities like Fragments, etc across Item type hierarchies. The properties of WinFS types in the schema are marked for content-indexing by the schema designer. Installing the content-index definitions includes parsing content-index definitions in the schema, generation of appropriate SQL statements for data extraction and storing the SQL statements.

Type definition language for defining content-index from a rich structured WinFS data type

Rich structured data for items in a file system that allows different kinds of data to be identified by metadata is mapped into a set of search properties for a desktop search service, which is a flat list. This is applicable to any rich structured data that should be mapped into search properties for a desktop search service. Included is an installation mechanism to install these mappings and an execution infrastructure for utilizing the generated SQL from the mappings to extract search properties from items.

Defining and extracting a flat list of search properties from a rich structured type

Growing community of inventors

Bellevue, WA, United States of America

Anurag Gupta