System and method

1. A system configured to manage, for a first time length, a plurality of events issued in response to a plurality of changes made to a database and execute a code corresponding to each of the plurality of changes in response to the plurality of events to process the plurality of events in chronological order, the system comprising:

one or more processors; and

at least one memory storing instructions, which when executed by the one or more processors, cause the system to:

manage status information for event processing as first execution status if a difference between a current time point and a time point at which a target event of the event processing occurs is not greater than a second time length, the second time length being shorter than the first time length;

perform control to retry the event processing on the target event if first event processing that is started in the first execution status as the event processing is not normally ended;

manage the status information for the event processing as second execution status if a difference between a current time point and the time point at which the target event of the event processing occurs is greater than the second time length; and

execute, without the control to retry, processing for failure notification of the event processing on the target event if second event processing that is started in the second execution status as the event processing is not normally ended.

2. The system according to claim 1 , wherein the instructions, when executed by the one or more processors, further cause the system to:

generate a second thread different from a first thread for executing the second event processing in the case in which the difference between the current time point and the time point at which the processing target event occurs is greater than the second time length;

perform, in the generated second thread, control to cancel the second event processing if it is determined that only a third time length has passed; and

execute, in the generated second thread, the processing for the failure notification if the second event processing is cancelled,

wherein the processing for the failure notification is executed in the first thread if the second event processing is not normally ended.

3. The system according to claim 2 , wherein the third time length is shorter than the second time length.

4. A system configured to manage, for a first time length, a plurality of events issued in response to a plurality of changes made to a database and execute a code corresponding to each of the plurality of changes in response to the plurality of events to process the plurality of events, the system comprising:

one or more processors; and

at least one memory storing instructions, which when executed by the one or more processors, cause the system to:

notify a first messaging service of the issued event in response to the issued event; and

control event processing on the issued event in response to an event notification from the first messaging service,

wherein in a case where the event processing is ended due to an occurrence of an exception or a timeout, a retry of the event processing is executed,

wherein in a case where the event processing is ended due to an occurrence of an exception or a timeout and a number of retries is greater than a predetermined number, processing for failure notification of the event processing on the issued event is executed, and

wherein in the processing for failure notification of the event processing, a second messaging service is notified, via a queue, of the event for which the processing has failed.

5. A method in a system configured to manage, for a first time length, a plurality of events issued in response to a plurality of changes made to a database and execute a code corresponding to each of the plurality of changes in response to the plurality of events to process the plurality of events in chronological order, the method comprising:

managing status information for event processing as first execution status if a difference between a current time point and a time point at which a target event of the event processing occurs is not greater than a second time length, the second time length being shorter than the first time length;

performing control to retry the event processing on the target event if first event processing that is started in the first execution status as the event processing is not normally ended;

managing the status information for the event processing as second execution status if a difference between a current time point and the time point at which the target event of the event processing occurs is greater than the second time length; and

executing, without the control to retry, processing for failure notification of the event processing on the target event if second event processing that is started in the second execution status as the event processing is not normally ended.

6. A method in a system configured to manage, for a first time length, a plurality of events issued in response to a plurality of changes made to a database and execute a code corresponding to each of the plurality of changes in response to the plurality of events to process the plurality of events, the method comprising:

notifying a first messaging service of the issued event in response to the issued event; and

controlling event processing on the issued event in response to an event notification from the first messaging service,

wherein in a case where the event processing is ended due to an occurrence of an exception or a timeout, a retry of the event processing is executed,

wherein in a case where the event processing is ended due to an occurrence of an exception or a timeout and a number of retries is greater than a predetermined number, processing for failure notification of the event processing on the issued event is executed, and

wherein in the processing for failure notification of the event processing, a second messaging service is notified, via a queue, of the event for which the processing has failed.