title: Syncing multiple Azure tables / containers in C# - whats the best practice?
body: <p>I have an Azure storage topology with multiple nodes which are mirrored, but can have different data depending on what user in what region is using what container node. </p>
  
  <p>My requirement is to sync the 3 node tables into a master node table. For example, if the table was Users, the three nodes (Node A, Node B, Node C) would populate the main User table with the result of a union of the three nodes, ignoring duplicates and removing not longer referenced rows. </p>
  
  <p>The "Big Hammer" approach (if I was doing this in SQL) would be to get the list of Users from the master table, the 3 lists of nodes, combine the nodes into a new collection, compare that collection to the master collection and perform a merge/union of the data, finally pushing that new merged and truncated collection up to that master node. </p>
  
  <p>My questions are:</p>
  
  <ol>
  <li>Is there a built in Azure way of doing this?</li>
  <li>Would doing this in C# as I desribed above be a good practice?</li>
  <li>What types of problems / risk can occur, and what considerations should be taken?</li>
  <li>Can you suggest a better solution to this problem; something tried and true (a design pattern maybe?)</li>
  <li>Can you provide a code sample for doing this in C#?</li>
  </ol>
  
  <p>I assume that if azure has no mechanism to help support this feature, then azure can be taken out of the mix and this becomes a pure C# List Manipulation problem.  </p>
  
  <p>Thanks much.</p>