Systems and methods for batch job execution in clustered environments using execution timestamp granularity to execute or refrain from executing subsequent jobs

A system for batch job execution, the system comprising:

• a first computer system comprising one or more processors configured to execute a first service;
• and
• a second computer system comprising one or more processors configured to execute a second service, wherein:
• the first service and the second service are each configured to:
• retrieve a job from a plurality of jobs stored in a single queue of a database, wherein the plurality of jobs comprise one or more jobs that are permitted to be executed and one or more jobs that are not permitted to be executed by the first and second service;
• determine that execution of a job of the plurality of jobs stored in the single queue of the database is permitted upon determining that the job is not associated with any execution timestamp that matches a respective system time, wherein a given execution timestamp is determined to match the respective system time when the respective system time falls within a granularity of the given execution timestamp, and
• execute the job upon determining that execution of the job is permitted, the first service is further configured to:
• identify a first job stored in the single queue;
• determine that execution of the first job by the first service is permitted by determining that the first job is not associated with any execution timestamp that matches the system time of the first service;
• upon determining that execution of the first job by the first service is permitted, generate a first execution timestamp having a granularity of two to nine seconds;
• record the generated first execution timestamp in the single queue such that the execution timestamp is associated with the first job;
• and
• execute the first job;
• the second service has access to the single queue to retrieve the first job and the first execution timestamp, and
• the second service is further configured to:
• identify the first job by querying the single queue;
• determine that the first job is associated with the first execution timestamp;
• determine whether a system time of the second service matches the first execution timestamp;
• and
• upon determining that the system time of the second service matches the first execution timestamp, refrain from executing the first job;
• wherein the first service is further configured to, prior to generating the first execution timestamp, determine that the first job is not associated with any execution timestamp matching a system time of the first computer system;
• and
• wherein the first job includes generation of a file representing a financial transaction.

A system for payment transfer, the system comprising:

• a first computer system comprising one or more processors configured to execute a first service instance;
• and
• a second computer system comprising one or more processors configured to execute a second service instance, wherein the first service and the second service are each configured to:
• retrieve a job from a plurality of jobs stored in a queue of a single database, wherein the plurality of jobs comprise one or more jobs that are permitted to be executed and one or more jobs that are not permitted to be executed by the first and second service;
• determine that execution of a job of the plurality of jobs stored in the single queue of the database is permitted upon determining that the job is not associated with any execution timestamp that matches a respective system time, wherein a given execution timestamp is determined to match the respective system time when the respective system time falls within a granularity of the given execution timestamp, and
• execute the job upon determining that execution of the job is permitted, the first service instance is further configured to:
• identify a first job stored in the single queue, the first job being generation of a file representing a transaction of transferring payment to a financial institution wherein the financial transaction comprises an automated clearing house file representing a person-to-person transaction of transferring funds from an account maintained by a bank to an account maintained by a receiving bank;
• determine that execution of the first job by the first service instance is permitted by determining that the first job is not associated with any execution timestamp that matches the system time of the first service instance;
• upon determining that execution of the first job by the first service instance is permitted, generate a first execution timestamp having a granularity of two to nine seconds;
• record the generated first execution timestamp in the single queue such that the first execution timestamp is associated with the first job;
• and
• execute the first job, thereby generating the file;
• and
• the second service instance has access to the single queue to retrieve the first job and the first execution timestamp, and
• the second service instance is further configured to:
• identify the first job by querying the single queue;
• determine that the first job is associated with the first execution timestamp;
• determine whether a system time of the second service instance matches the first execution timestamp to the granularity of the first execution timestamp;
• and
• upon determining that a system time of the second service instance matches the first execution timestamp to the granularity of the first execution timestamp, refrain from executing the first job;
• and
• wherein the first service is further configured to, prior to generating the first execution timestamp, determine that the first job is not associated with any execution timestamp matching a system time of the first computer system.