Org sync suspend and resume data sync

• US 10,540,369 B2
• Filed: 12/19/2016
• Issued: 01/21/2020
• Est. Priority Date: 12/19/2016
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Lee, Jong, Beyries, Patrick, Esaiarasan, Yamuna, Isaac, Jacob, Ulavapalli, Sindhubala
• Primary Examiner(s): Dwivedi, Mahesh H
• Application Number:
  US15/384,157
• Publication Number:
  US 20180173779A1
• Time in Patent Office: 1,128 Days
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Disclosed are some implementations of systems, apparatus, methods and computer program products for temporarily suspending data synchronization between a primary organization and a secondary organization. The primary organization may suspend data synchronization in response to a manual command. Alternatively, the primary organization may suspend data synchronization automatically upon detection of communication failure(s) between the primary organization and the secondary organization.

Claims

1. A system comprising:

a first database system implemented using a server system, the first database system configurable to cause;

processing a queue having at least one queue entry, the queue entry pertaining to a data update event, the data update event pertaining to the first database system and an update to be performed in relation to a second database system, wherein the queue entry indicates the update to be performed in relation to the second database system, the first database system being associated with a first organization and the second database system being associated with a second organization, the processing of the queue comprising;

obtaining a set of parameter values from the queue entry, and

initiating an update to at least one database of the second database system using the set of parameter values;

detecting a failure of a connection between the first database system and the second database system;

responsive to detecting the failure of the connection between the first database system and the second database system, automatically suspending the processing of the queue; and

after suspending the processing of the queue, detecting an active connection between the first database system and the second database system;

after detecting the active connection between the first database system and the second database system,

determining whether a threshold number of responses are received from the second database system; and

verifying that the active connection is not transient based, at least in part, on a result of determining whether the threshold number of responses are received from the second database system;

resuming the processing of the queue responsive to verifying that the active connection is not transient.

2. The system as recited in claim 1, the first database system further configurable to cause:

after detecting the active connection between the first database system and the second database system, sending a set of first communications to the second database system; and

wherein determining whether a threshold number of responses are received from the second database system includes ascertaining that the threshold number of second communications are received from the second database system in response to the set of first communications.

3. The system as recited in claim 1, the first database system further configurable to cause:

sending a set of one or more first communications to the second database system;

wherein detecting a failure of a connection between the first database system and the second database system includes ascertaining that a set of one or more second communications has not been received from the second database system in response to the set of first communications.

4. The system as recited in claim 1, the first database system further configurable to cause:

periodically monitoring, in real-time, the connection between the first database system and the second database system;

wherein an active connection between the first database system and the second database system is detected according to a result of periodically monitoring the connection between the first database system and the second database system.

5. The system as recited in claim 1, wherein processing the queue comprises:

calling an Application Programming Interface (API) of the second database system using the set of parameter values.

6. The system as recited in claim 1, wherein detecting a failure of a connection between the first database system and the second database system comprises detecting a failure during processing of the update to the database of the second database system using the set of parameter values.

7. The system as recited in claim 1, the set of parameter values indicating one or more of:

a) an identity of a particular data item or record to be added or deleted;

b) a data value of a field of a data record to be modified;

or

c) a type of the data update event, the type of the data update event including an addition, deletion, or modification.

8. The system as recited in claim 1, wherein determining whether a threshold number of responses are received from the second database system comprises:

determining that a sequence of the threshold number of second communications are received from the second database system in response to a sequence of first communications transmitted to the second database system.

9. A method, comprising:

processing, by one or more servers associated with a first organization, a queue having at least one queue entry, the queue entry pertaining to a data update event, the data update event pertaining to a first database system associated with the first organization and an update to be performed in relation to a second database system associated with a second organization, wherein the queue entry indicates the update to be performed in relation to the second database system associated with the second organization, the processing of the queue comprising;

obtaining a set of parameter values from the queue entry, and

initiating an update to a database of the second database system associated with the second organization using the set of parameter values;

detecting, by the one or more servers, a failure of a connection between the first database system and the second database system;

responsive to detecting, by the one or more servers, the failure of the connection between the first database system and the second database system, automatically suspending, by the one or more servers associated with the first organization, the processing of the queue; and

after suspending the processing of the queue, detecting, by the one or more servers, an active connection between the first database system and the second database system;

after detecting the active connection between the first database system and the second database system,

determining whether a threshold number of responses are received from the second database system; and

verifying that the active connection is not transient based, at least in part, on a result of determining whether the threshold number of responses are received from the second database system;

resuming, by the one or more servers associated with the first organization, the processing of the queue responsive to verifying that the active connection is not transient.

10. The method as recited in claim 9, further comprising:

sending a set of first communications to the second database system;

wherein determining whether a threshold number of responses are received from the second database system includes ascertaining that the threshold number of second communications are received from the second database system in response to the set of first communications.

11. The method as recited in claim 9, further comprising:

sending a set of one or more first communications to the second database system;

wherein detecting a failure of a connection between the first database system and the second database system includes ascertaining that a set of one or more second communications has not been received from the second database system in response to the set of first communications.

12. The method as recited in claim 9, further comprising:

periodically monitoring by the one or more servers, in real-time, the connection between the first database system and the second database system associated with the second organization;

wherein an active connection between the first database system and the second database system is detected according to a result of periodically monitoring the connection between the first database system and the second database system.

13. The method as recited in claim 9, wherein processing the queue comprises:

calling an Application Programming Interface (API) of the second database system using the parameter values.

14. The method as recited in claim 9, the set of parameter values indicating one or more of:

a) an identity of a particular data item or record to be added or deleted;

b) a data value of a field of a data record to be modified;

or

c) a type of the data update event, the type of the data update event including an addition, deletion, or modification.

15. The method as recited in claim 9, wherein determining whether a threshold number of responses are received from the second database system comprises:

determining that a sequence of the threshold number of second communications are received from the second database system in response to a sequence of first communications transmitted to the second database system.

16. A computer program product comprising computer-readable program code capable of being executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code comprising instructions configurable to cause:

processing a queue having at least one queue entry, the queue entry pertaining to a data update event, the data update event pertaining to a first database system and an update to be performed in relation to a second database system associated with a second organization, wherein the queue entry indicates the update to be performed in relation to the second database system, the first database system being associated with a first organization and the second database system being associated with a second organization, the processing of the queue comprising;

obtaining a set of parameter values from the queue entry, and

initiating an update to at least one database of the second database system using the set of parameter values;

detecting a failure of a connection between the first database system and the second database system;

responsive to detecting the failure of the connection between the first database system and the second database system, automatically suspending the processing of the queue; and

after suspending the processing of the queue, detecting an active connection between the first database system and the second database system;

after detecting the active connection between the first database system and the second database system,

determining whether a threshold number of responses are received from the second database system; and

verifying that the active connection is not transient based, at least in part, on a result of determining whether the threshold number of responses are received from the second database system;

resuming, the processing of the queue responsive to verifying that the active connection is not transient.

17. The computer program product as recited in claim 16, the program code comprising instructions further configured to cause:

sending a set of first communications to the second database system;

wherein determining whether a threshold number of responses are received from the second database system includes ascertaining that the threshold number of second communications are received from the second database system in response to the set of first communications.

18. The computer program product as recited in claim 16, the program code comprising instructions further configured to cause:

sending a set of one or more first communications to the second database system;

wherein detecting a failure of a connection between the first database system and the second database system includes ascertaining that a set of one or more second communications has not been received from the second database system in response to the set of first communications.

19. The computer program product as recited in claim 16, the program code comprising instructions further configured to cause:

periodically monitoring, in real-time, a connection between the first database and the second database system;

wherein an active connection between the first database system and the second database system is detected according to a result of periodically monitoring the connection between the first database system and the second database system.

20. The computer program product as recited in claim 16, wherein determining whether a threshold number of responses are received from the second database system comprises:

determining that a sequence of the threshold number of second communications are received from the second database system in response to a sequence of first communications transmitted to the second database system.