Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account
Read Performance Considerations - Comparing the Use of Amazon DynamoDB and Apache HBase for NoSQL

Read Performance Considerations

PDFRSS

With the launch of Amazon DynamoDB Accelerator (DAX), you can now get microsecond access to data that lives in Amazon DynamoDB. DAX is an in-memory cache in front of DynamoDB and has the identical API as DynamoDB.

Because reads can be served from the DAX layer for queries with a cache hit, and the table will only serve the reads when there is a cache miss, the provisioned read capacity units can be lowered for cost savings.

Tip: Based on the size of your tables and data access pattern, consider provisioning a single DAX cluster for multiple smaller tables or multiple DAX clusters for a single bigger table or a hybrid caching strategy that will work best for your application.

Need help?

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.