Client write event sequencing system in a federated database platform
Various embodiments are directed to a federated network and database platform that is configured to sequence client write events occurring among several autonomous software applications. The federated network and database platform includes a client event sequencing server that is configured to receive a migration corpus of client write events from at least one software application server and assign a back-date time stamp to each client write event of the migration corpus. Upon receiving a new client write event associated with the software application, the client event sequencing server is configured to assign a current time stamp to the new client write event and store the new client write event to a client event sequencing database in a manner that positions the new client write event relative to the back-dated migration corpus of client write events.
1. A computer-implemented method for sequencing client write events that are received in parallel from a client device to a client event sequencing server and at least one software application server that is configured to support a software application, the computer-implemented method comprising:
receiving a migration corpus of client write events to the client event sequencing server from the at least one software application server;
assigning, by the client event sequencing server, a back-date time stamp to each client write event of the migration corpus;
receiving a new client write event associated with the software application to the client event sequencing server;
assigning, by the client event sequencing server, a current time stamp to the new client write event; and
storing the new client write event to a client event sequencing database in relation to the migration corpus of client write events based at least in part on comparing the current time stamp assigned to the new client write event and the back-date time stamp assigned to each client write event of the migration corpus.
2. The computer-implemented method of claim 1 , wherein the client write events are received from the client device simultaneously to the client event sequencing server and the at least one software application server.
3. The computer-implemented method of claim 1 , wherein the client write events are received from the client device to the at least one software application server, and the at least one software application server subsequently provides copies of the client write events to the client event sequencing server.
4. The computer-implemented method of claim 1 , wherein the back-date time stamp designates one year prior to a copy operation start time determined by the client event sequencing server.
5. The computer-implemented method of claim 1 , wherein the back-date time stamp designates six months prior to a copy operation start time determined by the client event sequencing server.
6. The computer-implemented method of claim 1 , wherein the back-date time stamp is selected at a time (β) prior to a copy operation start time (t 0 ) minus any estimated network latency or device clock skew period (α).
7. The computer implemented method of claim 6 , wherein α ranges between 5 milliseconds and one year.
8. The computer-implemented method of claim 1 , wherein the migration corpus embodies a collection of client write events that have been stored to the at least one software application server while the client event sequencing server was down or offline.
9. The computer-implemented method of claim 1 , wherein the migration corpus embodies a collection of client write events that have been stored to the at least one software application server prior to activation of the client event sequencing server.
10. The computer-implemented method of claim 1 , wherein the client write event is associated with an authorization event.
11. The computer-implemented method of claim 1 , wherein, the client write is associated with a revocation event.
12. The computer-implemented method of claim 1 , further comprising:
receiving a second migration corpus of client write events to the client event sequencing server from the at least one software application server; and
assigning, by the client event sequencing server, a second back-date time stamp to each client write event of the second migration corpus of client write events.
13. The computer-implemented method of claim 12 , further comprising:
storing the new client write event to the client event sequencing database in relation to the migration corpus of client write events and the second migration corpus of client write events received from the at least one software application server based at least in part on comparing the current time stamp assigned to the new client write event, the back-date time stamp assigned to each client write event of the migration corpus, and the second back-date time stamp assigned to each client write event of the second migration corpus of client write events.
14. The computer-implemented method of claim 12 , wherein the back-date time stamp is selected at a time (β) prior to a copy operation start time (t 0 ) minus any estimated network latency or device clock skew period (α) and wherein the second back-date time stamp is selected at a time (β′) that is after the back-date time stamp (β) but prior to the copy operation start time (t 0 ) minus the estimated network latency or device clock skew period (α).
15. An apparatus for sequencing client write events that are received in parallel from a client device to a client event sequencing server and at least one software application server that is configured to support a software application, the apparatus comprising at least a processor, and a memory associated with the processor having computer coded instructions therein, with the computer coded instructions configured to, when executed by the processor cause the apparatus to:
receive a migration corpus of client write events to the client event sequencing server from the at least one software application server;
assign, by the client event sequencing server, a back-date time stamp to each client write event of the migration corpus;
receive a new client write event associated with the software application to the client event sequencing server;
assign, by the client event sequencing server, a current time stamp to the new client write event; and
store the new client write event to a client event sequencing database in relation to the migration corpus of client write events based at least in part on comparing the current time stamp assigned to the new client write event and the back-date time stamp assigned to each client write event of the migration corpus.
16. The apparatus of claim 15 , wherein the client write events are received from the client device simultaneously to the client event sequencing server and the at least one software application server.
17. The apparatus of claim 15 , wherein the client write events are received from the client device to the at least one software application server, and the at least one software application server subsequently provides copies of the client write events to the client event sequencing server.
18. The apparatus of claim 15 , wherein the back-date time stamp designates one year prior to a copy operation start time determined by the client event sequencing server.
19. The apparatus of claim 15 , wherein the back-date time stamp designates six months prior to a copy operation start time determined by the client event sequencing server.
20. The apparatus of claim 15 , wherein the back-date time stamp is selected at a time (β) prior to a copy operation start time (t 0 ) minus any estimated network latency or device clock skew period (α).
21. The apparatus of claim 20 , wherein α ranges between 5 milliseconds and one year.
22. The apparatus of claim 15 , wherein the migration corpus embodies a collection of client write events that have been stored to the at least one software application server while the client event sequencing server was down or offline.
23. The apparatus of claim 15 , wherein the migration corpus embodies a collection of client write events that have been stored to the at least one software application server prior to activation of the client event sequencing server.
24. The apparatus of claim 15 , wherein the client write event is associated with an authorization event.
25. The apparatus of claim 15 , wherein the client write event is associated with a revocation event.
26. The apparatus of claim 15 , wherein the computer coded instructions are further configured to, when executed by the processor, further cause the apparatus to:
receive a second migration corpus of client write events to the client event sequencing server from the at least one software application server; and
assign, by the client event sequencing server, a second back-date time stamp to each client write event of the second migration corpus.
27. The apparatus of claim 26 , wherein the computer coded instructions are further configured to, when executed by the processor, further cause the apparatus to: store the new client write event to the client event sequencing database in relation to the migration corpus of client write events and the second migration corpus of client write events received from the at least one software application server based at least in part on comparing the current time stamp assigned to the new client write event, the back-date time stamp assigned to each client write event of the migration corpus, and the second back-date time stamp assigned to each client write event of the second migration corpus.
28. The apparatus of claim 26 , wherein the back-date time stamp is selected at a time (β) prior to a copy operation start time (t 0 ) minus any estimated network latency or device clock skew period (α) and wherein the second back-date time stamp is selected at a time (β′) that is after the back-date time stamp (β) but prior to the copy operation start time (t 0 ) minus the estimated network latency or device clock skew period (α).
29. A computer program product for sequencing client write events that are received in parallel from a client device to a client event sequencing server and at least one software application server that is configured to support a software application, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising code instructions to:
receive a migration corpus of client write events to the client event sequencing server from the at least one software application server;
assign, by the client event sequencing server, a back-date time stamp to each client write event of the migration corpus;
receive a new client write event associated with the software application to the client event sequencing server;
assign, by the client event sequencing server, a current time stamp to the new client write event; and
store the new client write event to a client event sequencing database in relation to the migration corpus of client write events based at least in part on comparing the current time stamp assigned to the new client write event and the back-date time stamp assigned to each client write event of the migration corpus.