1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
It depends on the query pattern and the SLA they want to offer to this API:
- DynamoDB storing pre-calculated metrics is a good way to provide fast response time and high availability but the update logic is tricky to implement
- Elasticsearch can support updates and live aggregations with fast response time and high availability but simple metrics and it's easy to overload an Elasticsearch cluster
- Redshift/athena can be an option if query customization needs to be offered but isn't highly available and unpredictable queries are dangerous for concurrency. Compared to Athena, it can provides faster response time, SLA on query execution (no risk of contention on Athena clusters).
回答済み 5年前
関連するコンテンツ
- AWS公式更新しました 1年前
- AWS公式更新しました 2年前
- AWS公式更新しました 2年前