System, method and computer program product for routing messages to a server

• US 9,229,793 B2
• Filed: 04/22/2011
• Issued: 01/05/2016
• Est. Priority Date: 04/22/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Devadhar, Vijayanth
• Primary Examiner(s): Patel, Dhairya A
• Application Number:
  US13/092,710
• Publication Number:
  US 20110264765A1
• Time in Patent Office: 1,719 Days
• Field of Search: 709/212, 709/213, 709/214, 709/215, 709/216, 709/217, 709/218, 709/219
• US Class Current: 1/1
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions

Abstract

In accordance with embodiments, there are provided mechanisms and methods for routing messages to a server. These mechanisms and methods for routing messages to a server can enable dynamic data migration within a system, increased efficiency, improved user experience, avoidance of data loss, etc.

Claims

1. A computer program product, comprising a non-transitory computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to be executed by a computer to implement a method for routing messages to a server, the method comprising:

detecting by a system a request to migrate data of a client of the system from a first server of the system to a second server of the system;

in response to the request, migrating the data of the client from the first server of the system to the second server of the system;

during the migrating;

accessing one or more messages within a messaging element of the system separate from the first server and the second server, the one or more messages including requests to perform one or more tasks on one or more servers of the system;

identifying one or more of the messages queued within the messaging element of the system that include one or more tasks to be performed in association with the client of the system whose data is being migrated;

re-enqueueing the one or more identified messages within the messaging element of the system with a predetermined time delay;

detecting a conclusion to the migrating of the data of the client from the first server to the second server;

routing the one or more messages determined to be associated with the data being migrated from the messaging element to the second server and performing the one or more tasks requested by the one or more messages on the second server, when it is determined that the migrating of the data was successful; and

routing the one or more messages determined to be associated with the data being migrated from the messaging element to the first server and performing the one or more tasks requested by the one or more messages on the first server, when it is determined that the migrating of the data was not successful.

2. The computer program product of claim 1, wherein the migrating of the data includes migrating an organization of the system from the first server to the second server.

3. The computer program product of claim 1, wherein the messaging element includes a message queue of the system.

4. The computer program product of claim 3, further including receiving, at the message queue, an indication from the second server confirming whether each of the one or more messages routed to the second server has been performed on the second server of the system.

5. The computer program product of claim 1, wherein the one or more messages associated with the data include transient data.

6. The computer program product of claim 1, wherein a state associated with the data of the client of the system is changed to reflect that the migrating is currently being performed within the system.

7. The computer program product of claim 1, wherein a notification of the conclusion to the migrating includes an indication as to whether the migrating was successful or unsuccessful.

8. The computer program product of claim 1, wherein a result of the migrating is confirmed by a user.

9. The computer program product of claim 1, wherein a state associated with the data is changed to reflect that the migrating was successful and that the data is now on the second server of the system.

10. The computer program product of claim 1, wherein if the migrating is successful, new messages entering the messaging element that are directed toward the migrated data are routed to the second server.

11. The computer program product of claim 10, wherein the new messages, when received at the messaging element, are initially directed toward the first server, and are enqueued in the messaging element before being re-directed and routed toward the second server.

12. The computer program product of claim 1, wherein the system includes a multi-tenant on-demand database system.

13. The computer program product of claim 1, wherein the data that is migrated includes persistent data.

14. The computer program product of claim 1, wherein the migrating of the data is performed in response to a request by the client of the system.

15. The computer program product of claim 1, wherein the migrating of the data is performed automatically in response to one or more needs of the system.

16. The computer program product of claim 1, wherein routing for each type of the one or more messages is configured to be enabled or disabled, such that the routing of each of the one or more messages within the messaging element to the second server of the system is further based on a type of each of the one or more messages.

17. The computer program product of claim 1, wherein it is determined that one or more of the messages queued within the messaging element of the system are associated with the data being migrated from the first server to the second server when it is determined that the one or more messages manipulate the data being migrated from the first server to the second server.

18. A method, comprising:

detecting by a system a request to migrate data of a client of the system from a first server of the system to a second server of the system;

in response to the request, migrating the data of the client from the first server of the system to the second server of the system;

during the migrating;

accessing one or more messages within a messaging element of the system separate from the first server and the second server, the one or more messages including requests to perform one or more tasks on one or more servers of the system;

identifying one or more of the messages queued within the messaging element of the system that include one or more tasks to be performed in association with the client of the system whose data is being migrated;

re-enqueueing the one or more identified messages within the messaging element of the system with a predetermined time delay;

detecting a conclusion to the migrating of the data of the client from the first server to the second server;

routing the one or more messages determined to be associated with the data being migrated from the messaging element to the second server and performing the one or more tasks requested by the one or more messages on the second server, when it is determined that the migrating of the data was successful; and

routing the one or more messages determined to be associated with the data being migrated from the messaging element to the first server and performing the one or more tasks requested by the one or more messages on the first server, when it is determined that the migrating of the data was not successful.

19. A system, comprising:

at least one processor for;

detecting by the system a request to migrate data of a client of the system from a first server of the system to a second server of the system;

in response to the request, migrating the data of the client from the first server of the system to the second server of the system;

during the migrating;

accessing one or more messages within a messaging element of the system separate from the first server and the second server, the one or more messages including requests to perform one or more tasks on one or more servers of the system;

identifying one or more of the messages queued within the messaging element of the system that include one or more tasks to be performed in association with the client of the system whose data is being migrated;

re-enqueueing the one or more identified messages within the messaging element of the system with a predetermined time delay;

detecting a conclusion to the migrating of the data of the client from the first server to the second server;

routing the one or more messages determined to be associated with the data being migrated from the messaging element to the second server and performing the one or more tasks requested by the one or more messages on the second server, when it is determined that the migrating of the data was successful; and

routing the one or more messages determined to be associated with the data being migrated from the messaging element to the first server and performing the one or more tasks requested by the one or more messages on the first server, when it is determined that the migrating of the data was not successful.