laravel-eloquent-query-cache VS corcel

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)

It's here, but you may prefer Composer, the package manager for PHP:

Or alternatively - there are php packages for working directly with a wp database outside of wordpress: https://github.com/williarin/wordpress-interop, https://github.com/corcel/corcel

If you go this route, Corcel https://github.com/corcel/corcel is great.

You could also try something like Corcel for heavier emphasis on Laravel usage.

Another thing you may want to keep up your sleeve to transition between the two is Corcel, which lets you use WP for the backend/body, and Laravel to render the frontend/head of an application.

There are "bridges" like https://github.com/corcel/corcel

- https://github.com/corcel/corcel