Category: Laravel, PHP, api

Sometimes our applications do something so resource-taxing that it’s better to cache the result and return it. You’re totally fine with that approach, taking the result and caching it… until your Controller starts to pile up code in charge of cache management in multiple methods.
Newsletter

Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week

Community Partners