Sync as a service for cloud-based applications

Abstract

A technique provides sync capability as an independent backend service, which developers can include, at their option, in their cloud-based applications. In accordance with the improved technique, a sync service runs in a backend system in connection with a set of data. The sync service syncs changes in the set of data among application instances that have access to the set of data. Sync services may be specified selectively for different sets of data, e.g., by specifying syncing for one set of data but not for another set of data.

What is claimed is: 
     
         1 . A method, comprising:
 storing data on a remote computing device, the data being for an application executable on at least one client device;   storing settings in a database of the remote computing device, the settings configured to, on a per-container basis, sync data of the at least one client device with data of a container of the database; and   in response to (i) a change in data of the client device and (ii) the database including settings to sync the data of the at least one client device with the data of the container, updating the data of the container.   
     
     
         2 . The method of  claim 1 , further comprising providing entries in the database for respective ones of the containers, the entries indicating, on a per-container basis, whether to sync the respective containers. 
     
     
         3 . The method of  claim 2 , further comprising the entries indicating, on a per-container basis, whether the remote computing device employs a badging service, the badging service assigning a syncing status to respective containers on an individual basis and communicating the syncing status to the at least one client device. 
     
     
         4 . The method of  claim 3 , wherein the syncing status includes any of (i) sync complete, (ii) sync in progress, and (iii) sync failed. 
     
     
         5 . The method of  claim 2 , wherein the containers include a file-type container configured to store file-type data, and wherein storing the settings in the database includes specifying sync settings for the file-type container at an individual file level. 
     
     
         6 . The method of  claim 2 , wherein the containers include a file-type container configured to store file-type data, and wherein storing the settings in the database includes specifying sync settings for the file-type container at a folder level. 
     
     
         7 . The method of  claim 2 , wherein storing the settings includes receiving, via an API (Application Program Interface), an instruction specifying a particular container and providing settings for the particular container. 
     
     
         8 . The method of  claim 7 , wherein the containers include identifiers that uniquely identify the containers in the remote computing device, and wherein receiving the instruction includes the identifier of the particular container. 
     
     
         9 . The method of  claim 7 , wherein receiving the instruction providing sync settings for the particular data storage container includes an instruction to create the particular container in the remote computing device. 
     
     
         10 . A computing device, comprising memory and processing circuitry coupled to the memory, the computing device constructed and arranged to:
 store data on a remote computing device, the data being for an application executable on at least one client device;   store settings in a database of the remote computing device, the settings configured to, on a per-container basis, sync data of the at least one client device with data of a container of the database; and   in response to (i) a change in data of the client device and (ii) the database including settings to sync the data of the at least one client device with the data of the container, update the data of the container.   
     
     
         11 . The computing device of  claim 10 , further constructed and arranged to provide entries in the database for respective ones of the containers, the entries indicating, on a per-container basis, (i) whether to sync the respective containers and (ii) whether the computing device employs a badging service, the badging service configured to assign a syncing status to respective containers on an individual basis and communicate the syncing status to the at least one client device. 
     
     
         12 . The computing device of  claim 11 , wherein the containers include a file-type container configured to store file-type data, and wherein storing the settings in the database includes specifying sync settings for the file-type container at an individual file level. 
     
     
         13 . The computing device of  claim 11 , wherein the containers include a file-type container configured to store file-type data, and wherein storing the settings in the database includes specifying sync settings for the file-type container at a folder level. 
     
     
         14 . The computing device of  claim 11 , wherein storing the settings includes receiving, via an API (Application Program Interface), an instruction specifying a particular container and providing settings for the particular container. 
     
     
         15 . The computing device of  claim 14 , wherein the containers include identifiers that uniquely identify the containers in the computing device, and wherein receiving the instruction includes the identifier of the particular container. 
     
     
         16 . The computing device of  claim 14 , wherein receiving the instruction providing settings for the particular container includes an instruction to create the particular container in the computing device. 
     
     
         17 . A method, comprising:
 storing data on a remote computing device, the data being from an application executable on at least one client device;   storing settings in a database of the remote computing device, the settings configured to, on a per-container basis, enable syncing of data of the at least one client device with data of a container of the database; and   in response to a change in the data of the application of the client device, updating the data of the container.   
     
     
         18 . The method of  claim 17 , further comprising providing entries in the database for respective ones of the containers, the entries indicating, on a per-container basis, (i) whether to sync the respective containers and (ii) whether the remote computing device employs a badging service, the badging service configured to assign a syncing status to respective containers on an individual basis and communicate the syncing status to the at least one client device. 
     
     
         19 . The method of  claim 18 , wherein storing the settings includes receiving, via an API (Application Program Interface), an instruction specifying a particular container and providing settings for the particular container. 
     
     
         20 . The method of  claim 18 , wherein receiving the instruction providing settings for the particular container includes an instruction to create the particular container in the computing device.