[Windows 8.1 Desktop/Surface/Phone] connect client app to synchronization service(s)

Question

Hello Everybody!
I have to do some research about:  what is the best way to set up my project, I am new to Azure.
Situation:
I need to develop a service(s) and client app(s) that are able to synchronize data with each other: files and database changes. the client app(s) must have the capability  to work online / offline,  offline: when there is no internet connection
the data has to be stored local on the client device(s) and sync it later when there is active internet connection.
Client Devices:
Windows 8.1 (Windows 8.1 PC/Desktop)             
Windows 8.1 RT (Windows 8.1 Surface tablet)
Windows Phone 8.1 (Windows 8.1 Smart-phone)
We prefer to create the clients as a C# Store App Application.
Service:
This might become , if technically possible and preferable, a Azure service who main task it is to manage the communication between the server and the clients
Last days I spend my time doing research about how to get this done right.
I found several interesting techniques, some of got all the features I needed, and some just a few, but most of them aren't supported on one or more devices.
Microsoft Synchronization Framework
  Sync Toolkit WinRT / Phone
 Live SDK
Microsoft Synchronization Framework - got all the features I need but is not supported on Win RT and Phone
Sync Toolkit WinRT / Phone - Only Database Sync, is got bad documentation and unknown if supported on Desktop
Live SDK - Libraries to integrate with OneDrive, Only File Sync
Questions:
Does Azure support all the devices?
Is Azure supported in  C# Windows 8.1 Store Apps?
Is Azure suited to host a service I described?
Thanks in advanced!

Answer 1

Hi JelteV,
Thanks for posting!
Base on my experience, if you wan to synchronize data with each clients. I suggest you could refer to this solution:
1.Create a Sql Azure Database or storage account for storing your data 
2.Create a WCF service (web role or work role ) for communication between Client and Database
3.Set Up Table Structure (Important). I suggest you could add the deviceID and userID to distinguish the different data source. And add fields such as 'status', 'create time', 'latest update time' and so on.
For example, you client insert a record into local database and set the 'status' as ‘stay update’ or '1'. When your client connect the database and synchronize the data to server, you could set the 'status' as 'updating' or '2' . After
synchronization  data, you could change the status as 'updated' or '3'.
According to this idea, the client CRUD -> change the local state code
-> Sync data -> change the local state code ->
synchronization is complete -> change the local state code .If the mobile device need operate the data on the service , it also need to change the server status code to be updated, to be deleted (deleted should
be treated differently), the next time the client login server automatically checks the "state" as "pending action" and then synchronize the server to the client. So whether it is operating on a local table, or on the side of the direct
operation of the service, you can ensure that the data is synchronized two tables.
>>Does Azure support all the devices?
>>Is Azure supported in  C# Windows 8.1 Store Apps?
>>Is Azure suited to host a service I described?
From your question, I think you could create a WCF service host on azure, and call WCF service form different devices. And this method is supported the different device and win8.1 store app.
Also, please see this thread:
http://stackoverflow.com/questions/14595738/net-data-synchronization-between-multiple-clients-and-a-central-server
Hope this helps.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.