Efficient approach with the toleration of stale data to dynamically transform and unify data quality in client and server with continuous transaction flows

Discrepancies between client replication data quality information and server replication data quality information may be addressed by recording and transmitting the transaction processing rate for the server. The transaction processing rate may be used in conjunction with the number of transactions the server is behind to determine the transaction delay. The transaction delay may also be used in conjunction with the transaction processing rate to calculate the transaction lag. Using this information, the client and server may have a similar understanding of the replication data quality. This information may be cached and used to determine what servers requests should be routed to. Each time a client makes a request, the transaction processing rate and/or the transaction lag for the given server may be inserted into the replication data stream. The values inserted into the replication data stream may invalidate and replace the cached values.