Microsoft Technology Licensing, LLC

Google Inc.

Atul Adya

John R Douceur

William J Bolosky

Marvin Michael Theimer

Paramvir Bahl

Alastair Wolman

John David Dunagan

Gerald Cermak

Jitendra Dattatraya Padhye

Josh D Benaloh

Gideon Andreas Yuval

Lili Qiu

Ranveer Chandra

Sergey Melnik

Roger Wattenhofer

Gregory H Cooper

Daniel Sumers Myers

Arif Abdulhusein Merchant

Lidong Zhou

Ronnie Chaiken

Alexander Shraer

Kfir Lev-Ari

Vishesh Khemani

Abolade Gbadegesin

William Michael Zintel

Bruce Wayne Copeland

David C Steere

Colin Joseph Meek

Miguel Oom Temudo De Castro

John Reumann

Zlatko Michailov

Viraj B Mody

Thomas W Kleinpeter

Surajit J Chaudhuri

Vivek Ravindranath Narasayya

Per-Ake Larson

Philip Alan Bernstein

Stefan Saroiu

Jacob Rubin Lorch

Michael B Jones

Sanjay Agrawal

Jose A Blakeley

Marcus Jon Jager

Nicholas J Harvey

Michael Piatek

David Andrew Schultz

Jitendra D Padhey

Jitendra D Pahhye

Arunabha Ghosh

Methods, systems, and apparatus for automatic sharding and load balancing in a distributed data processing system. In one aspect, a method includes determining workload distribution for an application across worker computers and in response to determining a load balancing operation is required: selecting a first worker computer having a highest load measure relative to respective load measure of the other work computers; determining one or more move operations for a partition of data assigned to the first worker computer and a weight for each move operation; and selecting the move operation with a highest weight the selected move operation.

Weighted auto-sharing

Weighted auto-sharding

Application data is synchronized with a database where changes to object data maintained by an application is expressed according to an application schema. Changes to the object data are identified as corresponding to an entity schema. Changes to views of database tables are applied by translation rules to the set of changed entities. The database tables conforming to a database schema are thereafter updated.

View maintenance rules for an update pipeline of an object-relational mapping (ORM) platform

Technologies, systems, and methods for ordered message delivery that avoid message races or crisscrosses between communicating nodes. For example, if Node A sends message 3 towards Node B and, shortly thereafter, Node B sends message X to Node A, Node A would like to know whether or not message X reflects Node B's state after receiving message 3. If Node B received message 3 prior to sending message X, then proper state may be maintained between the nodes. But if messages 3 and X crisscrossed, or if message 3 was never properly received by Node B, then the state between the nodes may be corrupt. Technologies, systems, and methods are provided to avoid such corruption.

Crisscross cancellation protocol

A database update pipeline may be incorporated into a data access architecture for providing data services to applications, thereby bridging the gap between application data and data as persisted in databases. The update pipeline has the ability to translate changes made to object instances into data store change constructs, and carry those changes over to a data store. Such a pipeline can also advantageously perform the reverse operation, allowing applications to query using the database update pipeline, and receive materialized object instances.

Clients may subscribe to resources for the purpose of receiving notifications of changes in the resource (e.g., a file is added to a shared folder). Storing subscriptions within persistent storage provides data security in the event of a service failure, at the cost of high latency in accessing subscription data. An efficient method for tracking a resource is provided herein. A subscription service creates subscriptions and monitors resources for a client. Upon a subscribed resource change, a notification service stores a notification of the change into a queue associated with the client. Efficient resource tracking is achieved because notification and subscription data is stored in low latency soft memory. The notification service is configured to detect a failure in the notification service and/or subscription service. In the event a service fails, the client provides a recovery mechanism by resubscribing to resources with which the client has an interest.

Resource tracking

Technologies, systems, and methods for ordered message delivery that avoid message races or crisscrosses between communicating nodes. For example, if Node A sends messagetowards Node B and, shortly thereafter, Node B sends message X to Node A, Node A would like to know whether or not message X reflects Node B's state after receiving message. If Node B received messageprior to sending message X, then proper state may be maintained between the nodes. But if messagesand X crisscrossed, or if messagewas never properly received by Node B, then the state between the nodes may be corrupt. Technologies, systems, and methods are provided to avoid such corruption.

Technologies, systems, and methods for ordered message delivery that avoid message races or crisscrosses between communicating nodes. For example, if Node A sends message 3 towards Node B and, shortly thereafter, Node B sends message X to Node A. Node A would like to know whether or not message X reflects Node B's state after receiving message 3. If Node B received message 3 prior to sending message X, then proper state may be maintained between the nodes. But if messages 3 and X crisscrossed, or if message 3 was never properly received by Node B, then the state between the nodes may be corrupt. Technologies, systems, and methods are provided to avoid such corruption.

A distributed network system includes at least one server having memory and one or more processors. The server performs the following operations in connection with propagating object updates to respective client devices: receiving a first object update message from an application server, the first object update message including a first object identifier and a first object version; updating an object update record that includes the first object identifier using the first object version, wherein the object update record includes a first client identifier; propagating the first object version from the object update record to a client-object registration record that includes the first client identifier; and sending a second object update message to a first client device associated with the first client identifier, wherein the second object update message includes the first object identifier and the first object version.

Method and system for distributing object update messages in a distributed network system

A computer-implemented method in a distributed network system is disclosed. The computer-implemented method includes: receiving, at a server, a first object update message from a server-side application, wherein the first object update message includes a first object identifier; identifying, among a plurality of object-client registration records, an object-client registration record that includes the first object identifier; updating the object-client registration record in accordance with the first object update message; selecting a set of client identifiers associated with the first object identifier from the object-client registration record; and, for a first client identifier in the selected set of client identifiers, sending a second object update message to a first client device associated with the first client identifier, wherein the second object update message includes the first object identifier.

Method and system for migrating object update messages through synchronous data propagation

The application discloses a generic partitioning manager for partitioning resources across one or more owner nodes. In illustrated embodiments described, the partitioning manager interfaces with the one or more owner nodes through an owner library. A lookup node or application interfaces with the partitioning manager through the lookup library to lookup address or locations of the partitioned resources. In illustrated embodiments, resources are partitioned via the partitioning manager in response to lease request messages from an owner library. In illustrated embodiments, the lease grant message includes a complete list of the leases for the owner node.

Partitioning system including a generic partitioning manager for partitioning resources

A distributed network system includes at least one server and one client device, each having memory and one or more processors. The server performs the following operations: selecting a first client-object registration record including a first client identifier and a first object identifier; retrieving a pair of server-side object version and client-side object version from the first client-object registration record; determining a first set of incremental payloads to be delivered to the client device associated with the first client identifier in accordance with the pair of server-side object version and client-side object version; retrieving the first set of incremental payloads from a first object update record including the first object identifier; and sending a first object update message to the first client device, wherein the first object update message includes the first object identifier, the server-side object version and the retrieved first set of incremental payloads.

Method and system for delivering object update messages including payloads

A distributed network system includes a distributed server system and a plurality of client devices that are communicatively coupled to the distributed server system. The distributed server system includes multiple servers, each server including a set of client devices registered with the server. Through client re-registration, a client device can move its registration from one server to another server. Through server-side data replication, an object registration request submitted by a client device to a first server is forwarded to a second server without having the client device submitting the same request to the second server.

Method and system for maintaining client cache coherency in a distributed network system

Growing community of inventors

Redmond, WA, United States of America

Atul Adya