Redis vs ElastiCache (Valkey): Reserved Nodes, Database Savings Plans, and commitment risk

The blog post examines the complexities and risks associated with different commitment models for managing Redis and Valkey workloads using ElastiCache Reserved Nodes, AWS Database Savings Plans, and Redis Cloud annual plans. It highlights the challenge of commitment risk, where the gap between committed and actual usage can lead to stranded discounts and increased costs. ElastiCache Reserved Nodes provide node-level commitments but have limitations in flexibility regarding regions and node families, potentially resulting in stranded capacity when workloads shift. AWS Database Savings Plans offer broader flexibility but still involve risks related to overcommitted spend and specific database constraints. In contrast, Redis Cloud annual plans offer greater flexibility by tying discounts to Redis workloads rather than specific infrastructure, allowing usage to adapt to changing needs without stranding discounts. The blog emphasizes the importance of assessing commitment risks, including workload changes and regional expansions, before choosing a commitment model, and suggests that Redis Cloud plans may provide a more adaptable solution for evolving real-time data workloads.