Amazon MemoryDB Pricing

You are building an application that requires a database that provides fast data access to enable a  responsive, real-time user experience for a regional logistics company. The application has a total dataset size of 25 GB. On average, 3% of the data is updated every hour. You use a MemoryDB for Valkey architecture with one shard that includes one primary and one replica node per shard to meet the application requirements. You choose the db.r6g.xlarge node type as it has enough memory to fit the entire working dataset. You also choose to deploy your workload in China (Ningxia) Region. Additionally, you set your snapshot retention to 2 days enabling you to store the snapshot free of charge for the first day and charging you for snapshot storage for the additional day.

You work at a media and entertainment company and your team built an application that requires very low latency and high throughput. To meet these performance requirements, you use Amazon MemoryDB for Valkey as your primary database. The application is read-heavy and has a total dataset size of 50 GB consisting of 100 byte objects (includes Redis key, value and command size). The application is 80% reads and 20% writes, and approximately 50,000 transactions per second. You choose two shards of db.r6g.xlarge node type to have enough memory to fit the entire dataset in the cluster (50GB) and select one replica per shard to support the reads of the application and high availability. You also choose to deploy your workload across two availability zones (AZs) in China (Beijing) Region for high availability. Additionally, you set your snapshot retention to 2 days allowing you to store the snapshot free of charge for the first day and charging you for snapshot storage for the additional day. Your total charges are calculated as follows: