--- title: Don't push daily | daily.dev description: A critique of high-frequency frontend deployments, arguing that constantly pushing frontend changes causes unnecessary cache busting and degrades user... canonical: https://daily.dev/posts/don-t-push-daily-drwsxnfsm twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Don't push daily | daily.dev og:description: A critique of high-frequency frontend deployments, arguing that constantly pushing frontend changes causes unnecessary cache busting and degrades user... og:url: https://daily.dev/posts/don-t-push-daily-drwsxnfsm og:image: https://api.daily.dev/og/posts/DrwSXnFsM.png og:image:alt: Don't push daily 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. # Don't push daily **[ThePrimeTime](https://daily.dev/sources/primeagen)** · 1 min read · 0 upvotes · 0 comments ## Summary A critique of high-frequency frontend deployments, arguing that constantly pushing frontend changes causes unnecessary cache busting and degrades user experience by forcing repeated downloads of large bundles. The argument distinguishes between frontend and backend deployments: frontend changes rarely need to ship multiple times daily (except for production fixes), while backend deployments are less impactful as long as the HTTP interface remains stable. Spotify's 4,500 daily deploys are used as a jumping-off point for this perspective. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is deploying front-end changes very frequently considered bad practice? Frequent front-end deploys force cache busting on users, meaning browsers must re-download artifacts repeatedly, which degrades the user experience through unnecessary data usage and load times. This is especially costly for older projects that ship one large bundle rather than many small, independently cacheable bundles. Real production fixes justify fast deploys, but routine UI changes generally do not need that speed. _Weigh deploy cadence trade-offs like this by following frontend performance discussions on daily.dev._ ### Does deploying backend services frequently cause the same problems as frequent front-end deploys? No, backend deploy frequency matters much less because clients interact through a stable HTTP interface rather than downloading a changing artifact. As long as the REST service's request and response contracts remain identical, swapping out the underlying implementation or service version frequently causes no user-facing disruption. _Compare backend versus frontend deploy strategies with daily.dev when planning release cadence._ ## Similar posts on daily.dev - [the web server deployment model breaks at hobby scale](https://daily.dev/posts/the-web-server-deployment-model-breaks-at-hobby-scale-f2vq2xvo3) · Lobsters · 4 upvotes · 3 comments - [What front-end engineers need to know about AWS](https://daily.dev/posts/what-front-end-engineers-need-to-know-about-aws-a4zpc4n8d) · InfoWorld · 1 upvotes · 0 comments - [Frontend or Backend: Where Full-Stack Devs Spend Their Time](https://daily.dev/posts/frontend-or-backend-where-full-stack-devs-spend-their-time-gginyxzdd) · The New Stack · 0 upvotes · 0 comments - [Don’t let your backend write checks your frontend can’t cache](https://daily.dev/posts/don-t-let-your-backend-write-checks-your-frontend-can-t-cache-pd4qrqrxo) · Stack Overflow Blog · 70 upvotes · 2 comments - [JS-heavy approaches are not compatible with long-term performance goals](https://daily.dev/posts/js-heavy-approaches-are-not-compatible-with-long-term-performance-goals-g7unzk9jj) · Hacker News · 0 upvotes · 0 comments --- Tags: [#backend](https://daily.dev/tags/backend), [#cicd](https://daily.dev/tags/cicd), [#frontend](https://daily.dev/tags/frontend) [View this post on daily.dev](https://daily.dev/posts/don-t-push-daily-drwsxnfsm) ```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":"Don't push daily","url":"https://daily.dev/posts/don-t-push-daily-drwsxnfsm","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/don-t-push-daily-drwsxnfsm"},"datePublished":"2026-07-09T13:17:41.131Z","dateModified":"2026-09-14T08:39:30.948Z","description":"A critique of high-frequency frontend deployments, arguing that constantly pushing frontend changes causes unnecessary cache busting and degrades user...","image":"https://i.ytimg.com/vi/jCwdUxZrrCg/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/jCwdUxZrrCg/sddefault.jpg","isAccessibleForFree":true,"articleSection":"ThePrimeTime","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":"Organization","name":"ThePrimeTime","logo":"https://media.daily.dev/image/upload/s--J5-GjDeo--/f_auto/v1704628081/logos/primeagen.jpg","url":"https://daily.dev/sources/primeagen"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/don-t-push-daily-drwsxnfsm","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"backend,cicd,frontend","timeRequired":"PT1M","video":{"@type":"VideoObject","name":"Don't push daily","description":"A critique of high-frequency frontend deployments, arguing that constantly pushing frontend changes causes unnecessary cache busting and degrades user...","thumbnailUrl":"https://i.ytimg.com/vi/jCwdUxZrrCg/sddefault.jpg","uploadDate":"2026-07-09T13:17:41.131Z","duration":"PT1M","url":"https://api.daily.dev/r/DrwSXnFsM","embedUrl":"https://www.youtube.com/embed/jCwdUxZrrCg"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ThePrimeTime","item":"https://daily.dev/sources/primeagen"},{"@type":"ListItem","position":3,"name":"Don't push daily"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/don-t-push-daily-drwsxnfsm#faq","mainEntity":[{"@type":"Question","name":"Why is deploying front-end changes very frequently considered bad practice?","acceptedAnswer":{"@type":"Answer","text":"Frequent front-end deploys force cache busting on users, meaning browsers must re-download artifacts repeatedly, which degrades the user experience through unnecessary data usage and load times. This is especially costly for older projects that ship one large bundle rather than many small, independently cacheable bundles. Real production fixes justify fast deploys, but routine UI changes generally do not need that speed. Weigh deploy cadence trade-offs like this by following frontend performance discussions on daily.dev."}},{"@type":"Question","name":"Does deploying backend services frequently cause the same problems as frequent front-end deploys?","acceptedAnswer":{"@type":"Answer","text":"No, backend deploy frequency matters much less because clients interact through a stable HTTP interface rather than downloading a changing artifact. As long as the REST service's request and response contracts remain identical, swapping out the underlying implementation or service version frequently causes no user-facing disruption. Compare backend versus frontend deploy strategies with daily.dev when planning release cadence."}}]} ```