In cloud structure, we frequently prioritize efficiency, scale, and safety, however they will include stunning prices. In considered one of our Azure-based deployments, our group found {that a} seemingly easy caching resolution—designed solely to help primary key-value storage—was costing us greater than $5,000 monthly.
On the coronary heart of this value was our use of Azure Cache for Redis (Premium), which we had adopted to fulfill Digital Community (VNet) isolation necessities throughout a multi-region, multi-environment setup (manufacturing, growth, staging, and many others.). Every area and atmosphere required its personal Redis occasion to adjust to safety and infrastructure separation requirements. Though our caching wants had been minimal—lower than 200 MB of information that refreshed solely as soon as per hour—we had no alternative however to make use of Redis Premium for VNet help.
Why Redis Premium wasn’t the proper match
Initially, we used Azure Redis Commonplace, which was cost-effective and appropriate for our use case. Nonetheless, we quickly confronted a compliance requirement: All providers wanted to be remoted through VNet integration. Redis Commonplace, sadly, doesn’t help VNets. The one choice was to maneuver to the Premium tier, which begins at a considerably larger value level.
