Skip to main content

Command Palette

Search for a command to run...

What does cache busting aim to achieve, and how can it be done?

Published
1 min read
F
I am an Infrastructure and DevOps Engineer specializing in designing, building, and operating scalable, secure, and highly available cloud infrastructure. My core focus is on Microsoft Azure cloud platforms, Infrastructure as Code (IaC), and DevOps automation to support reliable production systems. I work across cloud infrastructure engineering, DevOps practices, and site reliability engineering (SRE) principles to ensure systems are resilient, observable, and optimized for performance, cost, and scalability. My experience includes designing and managing cloud environments across compute, networking, storage, identity, and security layers. I build Infrastructure as Code solutions using Terraform and Azure Resource Manager (ARM) templates to automate provisioning, configuration, and deployment of cloud resources. I am actively involved in improving system reliability through monitoring, logging, and incident response processes using tools such as Azure Monitor and cloud-native observability solutions. I also participate in on-call operations, production support, and incident management to ensure high availability of critical systems. Security is a core part of my engineering approach. I work with identity and access management (IAM), Azure Active Directory, and cloud security best practices to ensure infrastructure remains compliant, secure, and audit-ready in line with industry standards such as ISO 9001 and ISO 27001. I collaborate with cross-functional teams including software engineers, DevSecOps, and product teams to deliver infrastructure solutions for customer-facing applications and enterprise platforms. My technical interests and growth areas include: Cloud Infrastructure Engineering (Azure, AWS, GCP) Site Reliability Engineering (SRE) Platform Engineering Kubernetes & Container Orchestration Infrastructure as Code (Terraform, ARM) CI/CD Pipeline Automation Distributed Systems & System Design Cloud Security & Identity Management I am passionate about building systems that are not only scalable and efficient but also reliable and easy for engineers to use. I am continuously growing my expertise toward senior-level Infrastructure, SRE, and Platform Engineering roles, including global remote opportunities.

In order to avoid having to download files again when navigating between pages or refreshing the same page, browsers include a cache that temporarily stores them on websites. In order to instruct the browser to keep the file for a specific period of time, the server is configured to send headers. This preserves bandwidth while significantly speeding up websites.

The user's cache still refers to outdated files, which might lead to issues when website developers make changes to the site. If the cached CSS and JavaScript files are referring items that no longer exist, have relocated, or have been renamed, it could either leave them with outdated functionality or break a website.

The act of pushing the browser to download new files is known as cache busting. To accomplish this, give the new file a name distinct from the one on the old file.

Adding a query string at the end of the file is a typical way to make the browser download the file again.

src="js/script.js" => src="js/script.js?v=2"

Although the browser views it as a different file, it does not require changing the file name.

Thanks for reading...

Happy Coding!

More from this blog

Building Reliable Systems

93 posts

Insights on Infrastructure, DevOps, SRE, and building reliable systems at scale.