9417 SE Shoreland Dr, Bellevue, WA 98004 • (425)6815950
12522 65Th St, Kirkland, WA 98033 • (425)8274368 • (425)9688659
23514 24Th St, Sammamish, WA 98074 • (425)8368185 • (425)9610022
Redmond, WA
Hanover, NH
Kiona, WA
12522 NE 65Th St, Kirkland, WA 98033
Work
Position:
Clerical/White Collar
Education
Degree:
Associate degree or higher
Skills
Microsoft Sql Server • Web Services • Cloud Computing • Scalability • Distributed Systems • C# • Agile Methodologies • Windows Azure • Algorithms • Object Oriented Design • Ssrs • C++ • Python • Visual Studio • Sql
Yunxin Wu - Kirkland WA, US Shaoyu Zhou - Issaquah WA, US Lev Novik - Bellevue WA, US Irena Hudis - Bellevue WA, US Ashish B. Shah - Sammamish WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707203, 707102, 707201
Abstract:
Systems, methods, and computer program products for synchronizing items at replicas within a topology is disclosed. Items are stored in physical tables at the replicas. The physical table layouts at each replica can differ but are mapped to a common logical view. When a replica receives an indication that synchronization should be performed, the replica determines if changes have been made at the replica that should be mapped to the logical views. Replicas can facilitate this by comparing local change enumerations for changes made in physical tables to synchronization local change enumerations for changes in the logical views. Any changes that need to be synchronized are sent through the logical views to other replicas in the topology.
Lev Novik - Bellevue WA, US Irena Hudis - Bellevue WA, US Douglas B. Terry - San Carlos CA, US Ashish Shah - Sammamish WA, US Sanjay Anand - Sammamish WA, US Yunxin Wu - Kirkland WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707204, 707200, 707205
Abstract:
Systems and methods for replicating replicas in a sync community. Each replica in the sync community stores knowledge that represents changes the replica is aware of. Because each replica has its own knowledge, each replica does not need to know how many replicas are in the sync community or the topology of the sync community. By sending the knowledge with a request for changes, a replicating replica can enumerate the changes to replicate by comparing its knowledge with the received knowledge. After replication, the knowledge is updated. Knowledge may also include made-with-knowledge change IDs that permit each resolution to identify what a replica was aware of when a particular change was made. The made-with-knowledge values are used to detect conflicts during replication.
Lev Novik - Bellevue WA, US Michael R. Clark - Issaquah WA, US Yunxin Wu - Kirkland WA, US Douglas B. Terry - San Carlos CA, US Irena Hudis - Bellevue WA, US Tomas Talius - Sammamish WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707204, 707205, 709219, 709203, 709220
Abstract:
Methods for enabling mult-master synchronization of particular sets of data using filters. In a synchronization request, data including knowledge and filters may be supplied. A response may comprise data including changes that are identified by the filter and that have versions that are not known by the requestor.
Uniform Transfer Of Data Independent Of The Transfer Mechanism
Irena Hudis - Bellevue WA, US Alan Geoffrey Boshier - Redmond WA, US Lev Novik - Bellevue WA, US Yunxin Wu - Sammamish WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 9/46
US Classification:
719330, 719328, 715234, 707 1, 707100
Abstract:
A uniform data structure contains a number of data fields. Some of the data fields are dedicated to contain information concerning the transfer of a data segment of a particular type (such as an XML segment) using one particular transfer mechanism (such as transferring as a string or DOM object, or transfer using an interface such as ISAXContentHandler, ITextSource, ITextSink, or IDOMSink interfaces). Other data fields are dedicated to contain information concerning the transfer of data segments of the same particular type using another transfer mechanism. When a module is to transfer a data segment, the module will cause the unified data structure to be altered as appropriate for the desired transfer mechanism.
Extending Hierarchical Synchronization Scopes To Non-Hierarchical Scenarios
Lev Novik - Bellevue WA, US Douglas B. Terry - San Carlos CA, US Irena Hudis - Bellevue WA, US Jeremie E. Sartor - Redmond WA, US Shaoyu Zhou - Issaquah WA, US Tomas Talius - Sammamish WA, US Yunxin Wu - Kirkland WA, US Jin He - Redmond WA, US Mark Scurrell - Sammamish WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707204, 707 4, 707 8, 707200, 707201, 707203
Abstract:
Extending hierarchical synchronization (sync) scopes to non-hierarchical scenarios may involve a method for synchronizing differently organized data stores comprising mapping different physical organizations to similar logical organizations and utilizing an organization-based synchronization algorithm to synchronize the differently organized stores. Also, the uniqueness constraints of the organizations may be preserved as well as the parent-child ordering constraints of the organizations.
Vishal Kathuria - Woodinville WA, US Martin J. Sleeman - Redmond WA, US Robin Dhananjay Dhamankar - Redmond WA, US Hanumantha Rao Kodavalla - Sammamish WA, US Yunxin Wu - Kirkland WA, US Shaoyu Zhou - Issaquah WA, US Lev Novik - Bellevue WA, US Tomas Talius - Sammamish WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 12/00 G06F 17/30
US Classification:
707204, 707200, 707202
Abstract:
The subject invention relates to systems and/or methods that perform an authoritative and/or a non-authoritative restore of items in a data store. Backups are provided that include data associated with items and metadata related to the items that can include a history of operations and previous synchronizations to enable replications to converge after restoration. The operations that can be performed on the items include, for example, create, delete, update, move, etc. The items in the backups can be restored along with the metadata, which can be utilized to enable synchronization partners to converge based on a desired type of restoration.
Systems And Methods For Synchronizing With Multiple Data Stores
Ashish B. Shah - Sammamish WA, US Lev Novik - Bellevue WA, US Irena Hudis - Bellevue WA, US Darshatkumar A. Shah - Bellevue WA, US Yunxin Wu - Kirkland WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 15/16
US Classification:
709223, 707 1, 709219, 709221, 709224, 709220
Abstract:
Systems and methods for synchronizing data stores. A framework including a sync runtime enables consistent and manageable synchronization between a data store and multiple, diverse back end data stores. The sync runtime provides services such as change enumeration, conflict detection, metadata management, item ID matching, sync interruptability, and the like that are accessible to configurable adapters over an application programming interface. Each synchronizing data store can uses a sync controller to initialize an adapter that can access the services provided by the sync runtime. The sync controller can use a profile to configure each adapter. The profile can identify conflict resolution policies, synchronization filters, source and destination folders, sync direction, and the like.
Rajesh M. Rao - Sammamish WA, US Okechukwu C. Echeruo - Kent WA, US Irena Hudis - Bellevue WA, US Lev Novik - Bellevue WA, US Balan Sethu Raman - Redmond WA, US Yunxin Wu - Kirkland WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707821, 707203, 707204, 709248
Abstract:
A system and method for synchronizing a database having metadata and raw data. Metadata may be fully synchronized between two systems, with copies stored on both systems. Raw data may be selectively synchronized, so that a client system need not store all of the raw data locally. When disconnected, the client system may identify certain portions of the raw data to store locally, and such data may be synchronized when reconnected to a server system.
Microsoft Sql Server Web Services Cloud Computing Scalability Distributed Systems C# Agile Methodologies Windows Azure Algorithms Object Oriented Design Ssrs C++ Python Visual Studio Sql
Languages:
English Mandarin
Youtube
January 6, 2020
Duration:
4s
Jia Nailiang & Jia Yunxin - The King Sent Me ...
Duration:
3m 42s
zhang qiling & wu xie || constellation
"...your dna I can't forget" as usual all the info is at the end of th...