- 最新
- 最多得票
- 最多評論
From the description, it sounds like you are looking for a solution where you could temporarily cache data that can be consumed (read-only) by an API. Redis seems to be a potential fit, you could also look at Memcached. Below document has a comparison of Memcached and Redis https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/SelectEngine.html
Having said this, I would recommend you to review the requirement in a bit more detail and make a choice. Here are some areas you could think of and some questions you could ask yourselves (Not an exhaustive list) -
-
What is the type and structure of data? What is the volume of data? A reference on evaluating DynamoDB - https://aws.amazon.com/blogs/database/how-to-determine-if-amazon-dynamodb-is-appropriate-for-your-needs-and-then-plan-your-migration/
Redis is also a key-value pair data store.
-
How often this data changes? Can the external source propagate the incremental data changes to AWS i.e. Do you really need a daily full dump or incremental delta feeds?
-
Would persisting this data in RDS or DynamoDB serve any of your long term goals? (Based on the volume of reads, this could be a combination of 'RDS and Redis' or 'DynamoDB & DAX')?
-
What is the request volume? What volumes of requests query for same data as response (i.e. repeated reads)?
-
Do you have an API gateway for the API and does that already cache the API responses? Also, do you have any CDN (Content Delivery Network) already caching the API responses.
-
What are the data encryption/security, back-up and recovery (RTO and RPO), availability, durability requirements?
Use the below cost calculator to create an estimate for these 3 services to compare. Make sure you also consider the opportunity of reservations for these services - https://calculator.aws/#/
相關內容
- 已提問 6 個月前
AWS 官方已更新 2 年前- AWS 官方已更新 1 年前
Thank you!, That calculator is complex, there are some parameters that I dont have, we never be writting to the cache/repo (only reading from it) with full loads everyday from the source (external), we can adapt to any form of data structure, tabular from a db or key, value, we are not willing to persists this data, and suppose we are not weighting the benefits (caching) of responses times between one option or the other, we are being forced to use this because the owners of the source data do not want us to be openning db connections all day, just once a day. The question is what will be cheaper, keep in mind that we already have an RDS.