--- title: How We Cached Laravel News at the Edge with Fast Laravel description: A case study on how Laravel News implemented edge caching using Cloudflare and the Fast Laravel course. The site is high-traffic with constantly changing... canonical: https://daily.dev/posts/how-we-cached-laravel-news-at-the-edge-with-fast-laravel-rbgw6huba twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How We Cached Laravel News at the Edge with Fast Laravel | daily.dev og:description: A case study on how Laravel News implemented edge caching using Cloudflare and the Fast Laravel course. The site is high-traffic with constantly changing... og:url: https://daily.dev/posts/how-we-cached-laravel-news-at-the-edge-with-fast-laravel-rbgw6huba og:image: https://api.daily.dev/og/posts/RBgw6HUbA.png og:image:alt: How We Cached Laravel News at the Edge with Fast Laravel og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How We Cached Laravel News at the Edge with Fast Laravel **[Laravel News](https://daily.dev/sources/ln)** · [@ericlbarnes](https://daily.dev/ericlbarnes) · 4 min read · 5 upvotes · 0 comments ## Summary A case study on how Laravel News implemented edge caching using Cloudflare and the Fast Laravel course. The site is high-traffic with constantly changing content, so the team tackled three main challenges: removing unnecessary Livewire components in favor of plain Blade, keeping truly dynamic parts (toast notifications, sponsors, newsletter) dynamic via Alpine AJAX, and resolving conflicts between Laravel Cloud's built-in edge caching and direct Cloudflare rules. Cache busting is handled via Laravel model events for published articles, with a scheduled command covering timed posts. The approach is platform-agnostic — any app behind Cloudflare can benefit. Results showed cache hit rates jumping to a majority of requests, with spikes near 70%. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I cache a Laravel site at the edge with Cloudflare when parts of the page still need to be dynamic (like a newsletter form or rotating ads)? Use Alpine AJAX to swap out the truly dynamic pieces after the cached page loads, while converting unnecessary Livewire components back to plain Blade templates for anything that doesn't need reactivity. This isolates the few components (toast notifications, newsletter forms, rotating sponsor slots) that must stay dynamic, letting the rest of the page be served from Cloudflare's edge cache. _daily.dev surfaces practical caching writeups like this for developers shipping performance improvements on Laravel._ ### Why would running Cloudflare directly instead of Laravel Cloud's built-in edge caching be simpler for a Laravel app? Running two caching layers at once, Laravel Cloud's built-in edge caching and Cloudflare, can compete and make it unclear whose policies are active or how to cleanly bust the Cloud layer's cache. Bypassing Laravel Cloud's caching rules and using Cloudflare directly resolved the conflict while still providing the same underlying caching benefits. _developers weighing platform-level caching versus direct CDN control can track these tradeoffs on daily.dev._ ### Why doesn't Livewire work well with edge caching in Laravel? Livewire relies heavily on session state for its reactivity, which makes it incompatible with edge caching the way plain Blade, Inertia, or React components are. Jason McCreary has discussed with Caleb Porzio the idea of an anonymous Livewire component that could hydrate after a cached page loads, but as it stands Livewire remains the one exception to caching everything at the edge. _anyone architecting around Livewire's session dependency can follow related Laravel performance discussions on daily.dev._ ## Similar posts on daily.dev - [Speeding Up Laravel News With Cloudflare](https://daily.dev/posts/speeding-up-laravel-news-with-cloudflare-uyivtzspn) · Laravel News · 7 upvotes · 0 comments - [Installing Blaze](https://daily.dev/posts/installing-blaze-t5wukkn0s) · Larablog · 0 upvotes · 0 comments - [How We Built Laravel Wrapped](https://daily.dev/posts/how-we-built-laravel-wrapped-lnjvhibhm) · Laravel · 39 upvotes · 1 comments --- Tags: [#performance](https://daily.dev/tags/performance), [#laravel](https://daily.dev/tags/laravel), [#cloudflare](https://daily.dev/tags/cloudflare) [View this post on daily.dev](https://daily.dev/posts/how-we-cached-laravel-news-at-the-edge-with-fast-laravel-rbgw6huba) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How We Cached Laravel News at the Edge with Fast Laravel","url":"https://daily.dev/posts/how-we-cached-laravel-news-at-the-edge-with-fast-laravel-rbgw6huba","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-we-cached-laravel-news-at-the-edge-with-fast-laravel-rbgw6huba"},"datePublished":"2026-06-17T14:42:43.640Z","dateModified":"2026-09-14T10:00:17.774Z","description":"A case study on how Laravel News implemented edge caching using Cloudflare and the Fast Laravel course. The site is high-traffic with constantly changing...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/44c8e84e08f2d1e4dec839f384f7cf0d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/44c8e84e08f2d1e4dec839f384f7cf0d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Laravel News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Person","name":"Eric L. Barnes","url":"https://daily.dev/ericlbarnes","image":"https://media.daily.dev/image/upload/s--K6f982B3--/f_auto/v1755288662/avatars/avatar_9SjPngRVLKMb8ob1eVrqZ?_a=BAMClqZW0","description":"Founder of Laravel News","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":2400}},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-we-cached-laravel-news-at-the-edge-with-fast-laravel-rbgw6huba","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"performance,laravel,cloudflare","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Laravel News","item":"https://daily.dev/sources/ln"},{"@type":"ListItem","position":3,"name":"How We Cached Laravel News at the Edge with Fast Laravel"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-we-cached-laravel-news-at-the-edge-with-fast-laravel-rbgw6huba#faq","mainEntity":[{"@type":"Question","name":"How can I cache a Laravel site at the edge with Cloudflare when parts of the page still need to be dynamic (like a newsletter form or rotating ads)?","acceptedAnswer":{"@type":"Answer","text":"Use Alpine AJAX to swap out the truly dynamic pieces after the cached page loads, while converting unnecessary Livewire components back to plain Blade templates for anything that doesn't need reactivity. This isolates the few components (toast notifications, newsletter forms, rotating sponsor slots) that must stay dynamic, letting the rest of the page be served from Cloudflare's edge cache. daily.dev surfaces practical caching writeups like this for developers shipping performance improvements on Laravel."}},{"@type":"Question","name":"Why would running Cloudflare directly instead of Laravel Cloud's built-in edge caching be simpler for a Laravel app?","acceptedAnswer":{"@type":"Answer","text":"Running two caching layers at once, Laravel Cloud's built-in edge caching and Cloudflare, can compete and make it unclear whose policies are active or how to cleanly bust the Cloud layer's cache. Bypassing Laravel Cloud's caching rules and using Cloudflare directly resolved the conflict while still providing the same underlying caching benefits. developers weighing platform-level caching versus direct CDN control can track these tradeoffs on daily.dev."}},{"@type":"Question","name":"Why doesn't Livewire work well with edge caching in Laravel?","acceptedAnswer":{"@type":"Answer","text":"Livewire relies heavily on session state for its reactivity, which makes it incompatible with edge caching the way plain Blade, Inertia, or React components are. Jason McCreary has discussed with Caleb Porzio the idea of an anonymous Livewire component that could hydrate after a cached page loads, but as it stands Livewire remains the one exception to caching everything at the edge. anyone architecting around Livewire's session dependency can follow related Laravel performance discussions on daily.dev."}}]} ```