The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jul. 05, 2022
Filed:
Dec. 02, 2018
Microsoft Technology Licensing, Llc, Redmond, WA (US);
Karthik Raman, Sammamish, WA (US);
Momin Mahmoud Al-Ghosien, Sammamish, WA (US);
Bhalakumaaran Erode Ranganathan, Bellevue, WA (US);
Madhan Gajendran, Bengaluru, IN;
Ji Huang, Bothell, WA (US);
Atul Katiyar, Sammamish, WA (US);
Mikhail Mikhailovich Koltachev, Redmond, WA (US);
Sujit Vattathil Kuruvilla, Redmond, WA (US);
Digvijaysinh Govindbhai Makwana, Seattle, WA (US);
Subramanyam Pattipaka, Bellevue, WA (US);
Ovidiu Constantin Platon, Redmond, WA (US);
Ankur Savailal Shah, Redmond, WA (US);
Pankaj Sharma, Kirkland, WA (US);
Dharma Shukla, Bellevue, WA (US);
Shreshth Singhal, Seattle, WA (US);
Shireesh Kumar Thota, Redmond, WA (US);
MICROSOFT TECHNOLOGY LICENSING, LLC, Redmond, WA (US);
Abstract
Data services for workloads are often provided with a service level agreement specifying various performance guarantees (e.g., latency, availability, scalability, and consistency). Single-master architectures, in which updates to the data set are constrained to a single server, may limit the fulfillment of some performance guarantees. Presented herein are multi-master architectures, in which the server set is partitioned into at least two masters are permitted to update the data set and at least one non-master that is not permitted to update the data set. Non-masters that receive a request to update the data set forward the request to a master server for application to the data set. A master that receives the request applies it to the data set and propagates the update to other master and non-master servers. Conflicting updates may be resolved through a variety of conflict resolution techniques, optionally designating one master server as a conflict resolution server.