Abstract: A method for providing ingestion checkpointing from an event topic is disclosed. The method includes polling, via an event consumer, a message broker to initiate consumption of events from the event topic, the event topic relating to event storage; checkpointing, based on a result of the polling, the consumption of the events by writing corresponding data in multiple stages to a checkpointing durable store; inserting an event pending status for each of the events in an events time bucket table; committing, via the event consumer, the consumption of the events; initiating event processing for the events; and updating the events time bucket table with an event complete status when consumption of the events are completed.

Abstract: Various methods, apparatuses/systems, and media for data migration readiness of a target data source are disclosed. A processor receives a request having configurable filters and parameters from a consumer service to obtain data; invokes, in response to receiving the request, a service application programming interface (API) for the data; fetches requested data from a legacy data source in response to calling the service API; fetches data corresponding to the same request having the same configurable filters and parameters from a target data source; compare the fetched data from the legacy data source to the fetched data from the target data source; generates, in response to comparing, a data quality validation score; and when it is determined that the data quality validation score is equal to or more that predetermined threshold value, validates the target data source for migration readiness and terminating the legacy data source.

Abstract: A method for providing ingestion checkpointing from an event topic is disclosed. The method includes polling, via an event consumer, a message broker to initiate consumption of events from the event topic, the event topic relating to event storage; checkpointing, based on a result of the polling, the consumption of the events by writing corresponding data in multiple stages to a checkpointing durable store; inserting an event pending status for each of the events in an events time bucket table; committing, via the event consumer, the consumption of the events; initiating event processing for the events; and updating the events time bucket table with an event complete status when consumption of the events are completed.

Abstract: Various methods, apparatuses/systems, and media for data migration readiness of a target data source are disclosed. A processor receives a request having configurable filters and parameters from a consumer service to obtain data; invokes, in response to receiving the request, a service application programming interface (API) for the data; fetches requested data from a legacy data source in response to calling the service API; fetches data corresponding to the same request having the same configurable filters and parameters from a target data source; compare the fetched data from the legacy data source to the fetched data from the target data source; generates, in response to comparing, a data quality validation score; and when it is determined that the data quality validation score is equal to or more that predetermined threshold value, validates the target data source for migration readiness and terminating the legacy data source.

Abstract: A test tool includes a connection engine, a transformation engine, a validation engine, and a messaging engine. The connection engine connects to a first non-relational database, a second non-relational database, and a server. The transformation engine receives first and second messages from the first and second non-relational databases and transforms the second message into a JavaScript Object Notation message. The validation engine compares the first message with a server log stored on the server to determine whether information in the first message matches information in the server log and compares the JavaScript Object Notation message with the server log to determine whether information in the second message matches information in the server log. The messaging engine communicates a message indicating that information in the first message and the second message match information in the server log.