In cloud structure, we regularly prioritize efficiency, scale, and safety, however they’ll include shocking prices. In one in all 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 per 30 days.
On the coronary heart of this value was our use of Azure Cache for Redis (Premium), which we had adopted to satisfy Digital Community (VNet) isolation necessities throughout a multi-region, multi-environment setup (manufacturing, improvement, staging, and so forth.). Every area and surroundings 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 selection however to make use of Redis Premium for VNet help.
Why Redis Premium wasn’t the fitting match
Initially, we used Azure Redis Customary, which was cost-effective and appropriate for our use case. Nevertheless, we quickly confronted a compliance requirement: All companies wanted to be remoted through VNet integration. Redis Customary, sadly, doesn’t help VNets. The one possibility was to maneuver to the Premium tier, which begins at a considerably increased value level.
