A Laravel package that caches entire HTTP responses to dramatically speed up application performance.
Laravel ResponseCache is a PHP package that dramatically speeds up Laravel applications by caching entire HTTP responses. It intercepts successful GET requests, stores the complete response (including HTML, JSON, or other text-based content), and serves cached versions for subsequent identical requests without processing them through the full application stack.
Laravel developers building content-heavy applications, APIs, or websites where response times matter and where identical requests are common, such as blogs, e-commerce platforms, or content management systems.
Developers choose this package because it provides a simple, middleware-based approach to full-page caching that integrates seamlessly with Laravel's ecosystem, offers flexible caching strategies including grace periods for stale content, and significantly reduces server load without requiring complex configuration.
Speed up a Laravel app by caching the entire response
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Caches entire HTTP responses for successful GET requests, including headers and content, which dramatically reduces server load as shown in the route examples for /posts.
Supports standard caching and flexible caching with grace periods, allowing stale responses to be served while refreshing in the background, as demonstrated with FlexibleCacheResponse for routes like /dashboard.
Uses Laravel middleware for simple configuration, making it straightforward to apply caching to specific routes with configurable TTL without modifying controller logic.
Provides built-in mechanisms to clear cache on content changes or events, though implementation details require consulting the documentation for specific use cases.
Only caches successful GET requests with text-based content, excluding other HTTP methods like POST or PUT and non-text responses such as file downloads, limiting its scope for dynamic APIs.
For applications with frequent updates, cache invalidation can become complex, requiring custom event handling to avoid serving stale data, which isn't fully automated out of the box.
Performance and scalability depend on the underlying Laravel cache driver, which may need additional configuration or tuning for high-traffic or distributed environments.