laravel-mediable VS laravel-eloquent-query-cache

If I might offer an alternative, I am the maintainer of a similar competing library: laravel-mediable (https://github.com/plank/laravel-mediable). It covers all of the same bases as spatie's lib, though it has a different underlying architecture that makes it more suitable for a number of additional use cases. While medialibrary has a 1-many architecture which allows each file to be attached to one model, Mediable is many-to-many which allows files to be reused and referenced by multiple entities. It also offers full integration of the intervention library, and provides a system for keeping track of all of the variants of a given file that you have created.

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)