The post provides guidelines and recommendations for choosing the right instance type and number of shards for Amazon ElastiCache for Redis clusters based on the workload characteristics - memory-bound, CPU-bound (high RPS or high computational complexity), or network-bound.

<div>
<p>This article provides best practices and guidelines for sizing your Amazon ElastiCache for Redis clusters based on your workload characteristics.</p>
<p>Specifically, the article covers:</p>
<ul>
<li>Types of workloads (memory-bound, CPU-bound, network-bound)</li>
<li>ElastiCache for Redis instance types and their suitability for different workloads</li>
<li>Considerations for choosing the right instance size (concurrency, connections, TLS)</li>
<li>Guidelines for sizing memory-bound, network-bound, and CPU-bound workloads</li>
<li>Using Auto Scaling for dynamic scaling based on workload metrics</li>
<li>Conclusion and additional resources</li>
</ul>
</div>


Best practices for sizing your Amazon ElastiCache for Redis clusters

Related articles