Systems and methods for providing a delayed database cluster
In some aspects, the techniques described herein relate to a method including: receiving, at a data management platform, incoming data; writing the incoming data to a primary database cluster; executing an incremental backup operation, wherein the incremental backup operation generates an incremental backup of the primary database cluster; storing the incremental backup of the primary database cluster in a storage location; after a predetermined amount of time, executing an incremental restore operation on a delayed database cluster, wherein the incremental restore operation restores the incremental backup of the primary database cluster to the delayed database cluster; determining a data anomaly in the incoming data; and executing a failover command, wherein the failover command redirects database queries from the primary database cluster to the delayed database cluster.
1 . A method comprising:
receiving, at a data management platform, incoming data;
writing the incoming data to a primary database cluster;
executing an incremental backup operation, wherein the incremental backup operation generates an incremental backup of the primary database cluster;
storing the incremental backup of the primary database cluster in a storage location;
after a predetermined amount of time, executing an incremental restore operation on a delayed database cluster, wherein the incremental restore operation restores the incremental backup of the primary database cluster to the delayed database cluster;
providing the incremental backup to a user to provide the user with access to at least a portion of the incoming data from the delayed database cluster;
assigning a time-to-live (TTL) to data stored in the delayed database cluster, wherein the TTL defines a rolling window and data older than the TTL is deleted from the delayed database cluster;
determining a data anomaly in the incoming data; and
executing a failover command through an application programming interface (API), wherein the failover command redirects database queries from the primary database cluster to the delayed database cluster; and
triggering a message to be generated by the API and displayed by the API on a user interface of a client device that accesses the delayed database, and wherein the message indicates that data retrieved from the delayed database cluster is from a temporarily truncated dataset; and
upon the data anomaly being resolved, ceasing the message.
2 . The method of claim 1 , wherein the incoming data is streaming data received by a data consumption application, and wherein the data consumption application is configured as a consumer of a distributed event streaming platform.
3 . The method of claim 1 , wherein the storage location is a network storage location.
4 . The method of claim 1 , comprising:
executing a full backup operation, wherein the full backup operation generates a full backup of the primary database cluster.
5 . The method of claim 4 , comprising:
prior to executing the incremental restore operation on the delayed database cluster, initiating a one-time load of static database tables from the primary database cluster to the delayed database cluster.
6 . The method of claim 5 , comprising:
prior to executing the incremental restore operation on the delayed database cluster and after initiating the one-time load of static database tables from the primary database cluster to the delayed database cluster, executing a full restore operation on the delayed database cluster, wherein the full restore operation restores the full backup of the primary database cluster to the delayed database cluster.
7 . The method of claim 1 , wherein a second command through the API interface causes the API interface to direct the database queries back to the primary database cluster.
8 . A system comprising at least one computer including a processor and a memory, wherein the at least one computer is configured to:
receive, at a data management platform, incoming data;
write the incoming data to a primary database cluster;
execute an incremental backup operation, wherein the incremental backup operation generates an incremental backup of the primary database cluster;
store the incremental backup of the primary database cluster in a storage location;
after a predetermined amount of time, execute an incremental restore operation on a delayed database cluster, wherein the incremental restore operation restores the incremental backup of the primary database cluster to the delayed database cluster;
provide the incremental backup to a user to provide the user with access to at least a portion of the incoming data from the delayed database cluster;
assign a time-to-live (TTL) to data stored in the delayed database cluster, wherein the TTL defines a rolling window and data older than the TTL is deleted from the delayed database cluster;
determine a data anomaly in the incoming data; and
execute a failover command through an application programming interface (API), wherein the failover command redirects database queries from the primary database cluster to the delayed database cluster;
trigger a message to be generated by the API and displayed by the API on a user interface of a client device that accesses the delayed database, and wherein the message indicates that data retrieved from the delayed database cluster is from a temporarily truncated dataset; and
upon the data anomaly being resolved, cease the message.
9 . The system of claim 8 , wherein the incoming data is streaming data received by a data consumption application, and wherein the data consumption application is configured as a consumer of a distributed event streaming platform.
10 . The system of claim 8 , wherein the storage location is a network storage location.
11 . The system of claim 8 , comprising:
executing a full backup operation, wherein the full backup operation generates a full backup of the primary database cluster.
12 . The system of claim 11 , wherein the at least one computer is configured to:
prior to executing the incremental restore operation on the delayed database cluster, initiate a one-time load of static database tables from the primary database cluster to the delayed database cluster.
13 . The system of claim 12 , wherein the at least one computer is configured to:
prior to executing the incremental restore operation on the delayed database cluster and after initiating the one-time load of static database tables from the primary database cluster to the delayed database cluster, execute a full restore operation on the delayed database cluster, wherein the full restore operation restores the full backup of the primary database cluster to the delayed database cluster.
14 . The system of claim 8 , wherein a second command through the API interface causes the API interface to direct the database queries back to the primary database cluster.
15 . A non-transitory computer readable storage medium, including instructions stored thereon, which instructions, when read and executed by one or more computer processors, cause the one or more computer processors to perform steps comprising:
receiving, at a data management platform, incoming data;
writing the incoming data to a primary database cluster;
executing an incremental backup operation, wherein the incremental backup operation generates an incremental backup of the primary database cluster;
storing the incremental backup of the primary database cluster in a storage location;
after a predetermined amount of time, executing an incremental restore operation on a delayed database cluster, wherein the incremental restore operation restores the incremental backup of the primary database cluster to the delayed database cluster;
providing the incremental backup to a user to provide the user with access to at least a portion of the incoming data from the delayed database cluster;
assigning a time-to-live (TTL) to data stored in the delayed database cluster, wherein the TTL defines a rolling window and data older than the TTL is deleted from the delayed database cluster;
determining a data anomaly in the incoming data; and
executing a failover command through an application programming interface (API), wherein the failover command redirects database queries from the primary database cluster to the delayed database cluster;
trigger a message to be generated by the API and displayed by the API on a user interface of a client device that accesses the delayed database, and wherein the message indicates that data retrieved from the delayed database cluster is from a temporarily truncated dataset; and
upon the data anomaly being resolved, cease the message.
16 . The non-transitory computer readable storage medium of claim 15 , wherein the incoming data is streaming data received by a data consumption application, and wherein the data consumption application is configured as a consumer of a distributed event streaming platform.
17 . The non-transitory computer readable storage medium of claim 15 , wherein the storage location is a network storage location.
18 . The non-transitory computer readable storage medium of claim 15 , comprising:
executing a full backup operation, wherein the full backup operation generates a full backup of the primary database cluster.
19 . The non-transitory computer readable storage medium of claim 18 , comprising:
prior to executing the incremental restore operation on the delayed database cluster, initiating a one-time load of static database tables from the primary database cluster to the delayed database cluster.
20 . The non-transitory computer readable storage medium of claim 19 , comprising:
prior to executing the incremental restore operation on the delayed database cluster and after initiating the one-time load of static database tables from the primary database cluster to the delayed database cluster, executing a full restore operation on the delayed database cluster, wherein the full restore operation restores the full backup of the primary database cluster to the delayed database cluster.