Methods and systems for batch processing in an on-demand service environment

• US 9,507,627 B2
• Filed: 10/23/2013
• Issued: 11/29/2016
• Est. Priority Date: 04/20/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Fee, Gregory D., Gallagher, William J.
• Primary Examiner(s): Tang, Kenneth
• Application Number:
  US14/061,545
• Publication Number:
  US 20140053160A1
• Time in Patent Office: 1,133 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 2209/5013 Request control
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

In accordance with embodiments disclosed herein, there are provided mechanisms and methods for batch processing in an on-demand service environment. For example, in one embodiment, mechanisms include receiving a processing request for a multi-tenant database, in which the processing request specifies processing logic and a processing target group within the multi-tenant database. Such an embodiment further includes dividing or chunking the processing target group into a plurality of processing target sub-groups, queuing the processing request with a batch processing queue for the multi-tenant database among a plurality of previously queued processing requests, and releasing each of the plurality of processing target sub-groups for processing in the multi-tenant database via the processing logic at one or more times specified by the batch processing queue.

Claims

1. A method in a system having at least a processor and a memory therein for executing instructions, wherein the method comprises:

communicating, via a request interface of the system, with a remotely connected client device during a synchronous request/reply session established between the client device and the request interface of the system;

receiving at the request interface of the system, a request for synchronous processing from the remotely connected client device, the request specifying a real-time transaction request to retrieve or store data on behalf of the client device at a database system communicably interfaced with the system;

rejecting or terminating the real-time transaction request;

receiving, at the system, a batch processing request from the remotely connected client device, the batch processing request re-submitting the real-time transaction request to retrieve or store data on behalf of the client device at a database system as a batch processing request to be completed via asynchronous processing at the database system;

dividing the batch processing request into a plurality of processing target sub-groups;

queuing the batch processing request within a batch processing queue;

releasing each of the plurality of processing target sub-groups for processing by the database system at one or more times specified by the batch processing queue; and

sending a completion status to an originator of the batch processing request, the completion status indicating a successful or unsuccessful completion for each processing target sub-group, wherein each completion status comprises a status selected from the group comprising;

complete and committed without error;

complete and committed after re-try due to excessive use of resources;

complete and committed after re-try due to excessive workload at the database system; and

abort due to one or more errors for the respective processing target sub-group, wherein any database transaction error for the respective processing target sub-group prevents committing transaction associated with the respective processing target sub-group to the database system.

2. The method of claim 1, wherein the database system embodies a multi-tenant database system having data stored therein on behalf of multiple customer organizations;

and

wherein the method further comprises running each of the plurality of processing target sub-groups released for processing in the multi-tenant database system concurrently with a plurality of other database transactions to be processed synchronously in the multi-tenant database system on behalf of other customer organizations other than a one customer organization associated with the remotely connected client device having submitted the batch processing request.

3. The method of claim 1:

wherein the database system embodies a multi-tenant database system having data stored therein on behalf of multiple customer organizations;

wherein the batch processing request specifies customer logic for one of the multiple customer organizations, the customer logic to be applied to processing in the multi-tenant database system in fulfillment of the batch processing request; and

wherein the customer logic is applied to each of the plurality of processing target sub-groups in the multi-tenant database system when released for processing by the batch processing queue.

4. The method of claim 1, wherein releasing each of the plurality of processing target sub-groups for processing by the database system at the one or more times specified by the batch processing queue comprises:

waiting until the queued batch processing request reaches a top position in the batch processing queue;

selecting an unprocessed one of the plurality of processing target sub-groups; and

releasing the selected unprocessed one of the plurality of processing target sub-groups to the database system.

5. The method of claim 4, further comprising:

re-queuing the batch processing request within the batch processing queue when at least one of the plurality of processing target sub-groups for the batch processing request remain unprocessed; and

iteratively repeating the waiting, selecting, and releasing operations until all of the plurality of processing target sub-groups for the processing request are processed in the database system.

6. The method of claim 5, further comprising:

sending a completion notification to the originator of the batch processing request outside of the synchronous request/reply session established between the client device and the request interface of the system, wherein the completion notification comprises a completion report specifying;

each of the plurality of processing target sub-groups released for processing in the database system; and

the completion status for each of the plurality of processing target sub-groups indicating the successful or unsuccessful completion for each processing target sub-group.

7. The method of claim 1, wherein queuing the processing request with the batch processing queue comprises:

generating a reference message for the processing request in the batch processing queue, wherein the reference message specifies;

the one or more processing target sub-groups,

a processing state for each of the one or more processing target sub-groups,

a pointer to each of the one or more processing target sub-groups, and

a pointer to the processing logic to be applied to each of the one or more processing target sub-groups; and

wherein the batch processing queue manages a list of pending batch processing requests to be asynchronously processed against the database system, each pending batch processing requests having one or more processing target sub-groups in an unprocessed state.

8. The method of claim 1:

wherein queuing the batch processing request within the batch processing queue comprises submitting a reference message for the batch processing request to the batch processing queue;

wherein releasing each of the plurality of processing target sub-groups for processing in the database system comprises de-queuing the reference message from the batch processing queue; and

wherein the method further comprises submitting a new reference message for the processing request to the batch processing queue as part of a commit process for the respective processing target sub-group released for processing in the database system, wherein the new reference message corresponds to a next unprocessed one of the plurality of processing target sub-groups for the processing request when at least one processing target sub-group for the processing request remains in an unprocessed state.

9. The method of claim 1, wherein rejecting or terminating the real-time transaction request comprises rejecting or prematurely terminating the real-time transaction request based on a determined inability of the database system to complete the real-time transaction request prior to a session timeout for the synchronous request/reply session established between the client device and the request interface of the system.

10. The method of claim 1, wherein rejecting or terminating the real-time transaction request comprises rejecting or prematurely terminating the real-time transaction request based on the real-time transaction request being too large a quantity of transactions required to complete the real-time transaction request or having a determined computationally intensive resource requirement in excess of a threshold or processing duration in excess of a permissible time period for the synchronous request/reply session established between the client device and the request interface of the system.

11. The method of claim 1, wherein rejecting or terminating the real-time transaction request further comprises responding to the remotely connected client device via the synchronous request/reply session with an error message indicating the real-time transaction request is too large for processing within the synchronous request/reply session.

12. The method of claim 1, wherein rejecting or terminating the real-time transaction request further comprises:

responding to the remotely connected client device via the synchronous request/reply session with an error message indicating the real-time transaction request will not be processed synchronously; and

sending an indication to the remotely connected client device that the real-time transaction request may be re-submitted as the batch processing request via batch processing interface.

13. The method of claim 1, wherein receiving, at the system, a batch processing request from the remotely connected client device comprises:

receiving the batch processing request at a batch processing interface of the system; and

enqueuing the batch processing request within the batch processing queue amongst a plurality of previously queued processing requests.

14. The method of claim 13, wherein a first portion of the previously queued processing requests constitute a plurality of real-time transaction request and wherein a second portion of the previously queued processing requests constitute transactions associated with multiple processing target sub-groups, each divided from batch processing requests submitted for processing via the database system.

15. The method of claim 1, wherein receiving the batch processing request from the remotely connected client device comprises receiving a header with the batch processing request, the header indicating the workload associated with the batch processing request is to be conducted via asynchronous batch processing.

16. The method of claim 1, wherein receiving the batch processing request from the remotely connected client device comprises receiving a header with the batch processing request, the header having therein an asynchronous processing parameter or flag may set for the batch processing request, the asynchronous processing parameter or flag indicating the workload associated with the batch processing request is to be conducted via asynchronous batch processing.

17. The method of claim 1, further comprising:

sending a completion notification to the originator of the batch processing request outside of the synchronous request/reply session established between the client device and the request interface of the system.

18. A method comprising:

receiving a processing request for a multi-tenant database, wherein the processing request specifies processing logic and a processing target group within the multi-tenant database;

dividing the processing target group into a plurality of processing target sub-groups;

queuing the processing request with a batch processing queue for the multi-tenant database among a plurality of previously queued processing requests;

releasing each of the plurality of processing target sub-groups for processing in the multi-tenant database via the processing logic at one or more times specified by the batch processing queue;

wherein releasing each of the plurality of processing target sub-groups for processing at the one or more times specified by the batch processing queue comprises;

(i) waiting until the queued processing request reaches a top position in the batch processing queue, (ii) selecting an unprocessed one of the plurality of processing target sub-groups, (iii) releasing the selected unprocessed one of the plurality of processing target sub-groups to the multi-tenant database;

wherein the method further comprises;

re-queuing the processing request with the batch processing queue when at least one of the plurality of processing target sub-groups for the processing request remain unprocessed;

iteratively repeating the waiting, selecting, and releasing operations until all of the plurality of processing target sub-groups for the processing request are processed in the multi-tenant database;

sending a completion notification to the originator of the processing request, wherein the completion notification comprises a completion report specifying;

(i) each of the plurality of processing target sub-groups released for processing in the multi-tenant database and (ii) a completion status for each of the plurality of processing target sub-groups indicating a successful or unsuccessful completion for each processing target sub-group; and

wherein each completion status comprises a status selected from the group comprising;

complete and committed without error;

complete and committed after re-try due to excessive use of resources;

complete and committed after re-try due to excessive multi-tenant database workload; and

abort due to one or more errors for the respective processing target sub-group, wherein any database transaction error for the respective processing target sub-group prevents committing transaction associated with the respective processing target sub-group to the multi-tenant database.

19. Non-transitory computer readable storage media having instructions stored thereupon that, when executed by a processor of a system, the instructions cause the system to perform operations comprising:

communicating, via a request interface of the system, with a remotely connected client device during a synchronous request/reply session established between the client device and the request interface of the system;

receiving at the request interface of the system, a request for synchronous processing from the remotely connected client device, the request specifying a real-time transaction request to retrieve or store data on behalf of the client device at a database system communicably interfaced with the system;

rejecting or terminating the real-time transaction request;

receiving, at the system, a batch processing request from the remotely connected client device, the batch processing request re-submitting the real-time transaction request to retrieve or store data on behalf of the client device at a database system as a batch processing request to be completed via asynchronous processing at the database system;

dividing the batch processing request into a plurality of processing target sub-groups;

queuing the batch processing request within a batch processing queue;

releasing each of the plurality of processing target sub-groups for processing by the database system at one or more times specified by the batch processing queue; and

sending a completion status to an originator of the batch processing request, the completion status indicating a successful or unsuccessful completion for each processing target sub-group, wherein each completion status comprises a status selected from the group comprising;

complete and committed without error;

complete and committed after re-try due to excessive use of resources;

complete and committed after re-try due to excessive workload at the database system; and

abort due to one or more errors for the respective processing target sub-group, wherein any database transaction error for the respective processing target sub-group prevents committing transaction associated with the respective processing target sub-group to the database system.

20. The non-transitory computer readable storage media of claim 19, wherein the instructions cause the system to perform operations further comprising:

sending a completion notification to the originator of the batch processing request outside of the synchronous request/reply session established between the client device and the request interface of the system.

21. A system comprising:

a processor and memory to execute instructions;

a request interface to communicate with a remotely connected client device during a synchronous request/reply session established between the client device and the request interface of the system;

the request interface to receive a request for synchronous processing from the remotely connected client device, the request to specify a real-time transaction request to retrieve or store data on behalf of the client device at a database system communicably interfaced with the system;

a batch processing governor to reject or terminate the real-time transaction request;

the request interface to receive a batch processing request from the remotely connected client device, the batch processing request being a re-submission of the real-time transaction request to retrieve or store data on behalf of the client device at a database system as a batch processing request to be completed via asynchronous processing at the database system;

a request chunker to chunk the batch processing request into a plurality of processing target sub-groups;

a batch processing queue to queue the batch processing request within a batch processing queue;

a release agent to release each of the plurality of processing target sub-groups for processing by the database system at one or more times specified by the batch processing queue; and

the request interface to further send a completion status to an originator of the batch processing request, the completion status to indicate a successful or unsuccessful completion for each processing target sub-group, wherein each completion status comprises a status selected from the group comprising;

complete and committed without error;

complete and committed after re-try due to excessive use of resources;

complete and committed after re-try due to excessive workload at the database system; and

abort due to one or more errors for the respective processing target sub-group, wherein any database transaction error for the respective processing target sub-group prevents committing transaction associated with the respective processing target sub-group to the database system.

22. The system of claim 21, further comprising:

the request interface to send a completion notification to the originator of the batch processing request outside of the synchronous request/reply session established between the client device and the request interface of the system.