laravel-eloquent-query-cache VS laravel-model-caching

Also this package (there are many alternatives) handing cache option now, https://github.com/renoki-co/laravel-eloquent-query-cache

We're beginning to hit a threshold for queries and need to start implementing a query cache fairly soon using something like: https://github.com/renoki-co/laravel-eloquent-query-cache. We already have Redis running for our general Caching and Session storage and that sits on a dedicated Redis instance in AWS. We take a small performance hit from network latency overall, but its not that noticeable, however we are about to add in-transit encryption which further decrease performance.

I didn't want to use the query to cache it because I still want to have control of the key, it's mainly an alias for Cache::remember. If you want that kind of cache, there are already some packages out there (like this https://github.com/renoki-co/laravel-eloquent-query-cache)

I've had some success with the laravel-model-caching package: https://github.com/GeneaLabs/laravel-model-caching

I also use this super handy package which puts Redis in between your models so rather than writing right to the DB the app interacts with Redis which then writes to the DB when it can thus saving so much load time: https://github.com/GeneaLabs/laravel-model-caching

Thank you for concerns. But don't have to. And I found https://github.com/GeneaLabs/laravel-model-caching only. but it has some conflicts with another packages. So I can not adopt. Thanks.