Is the Ti-Redis component feasible

Redis is great, but no matter how carefully we handle data, it is inevitable that there will be inconsistencies between cached data and actual data.

I have an idea here, I'm not sure if it's feasible:
`If Tidb were to implement a separate ti redis component (similar to ti flash), could it be possible to configure a large amount of cached data at the database level for buffering, and give specific parameters that can be configured at any time when querying data with code that prioritize querying from ti redis? This greatly liberates development and maintenance personnel, ensures stability, and greatly improves efficiency`

-----------

If technically impossible, please close this issue