DynamoDB + Elasticsearch: is that a good architecture pattern?

0

While playing with AWS Amplify, I was looking for the most appropriate architecture pattern, which would allow me to have the following:

  1. scalable and reliable DB to handle CRUD operations (DynamoDB rocks here)
  2. complex querying and filtering, where data access patterns are not strictly defined or unknown (Elasticsearch wins here)

So obviously I am hooked by the idea of streaming DynamoDB data to Elasticsearch for ALL queries and keeping DynamoDB with read/write operations only.

What are the pros and cons of this architecture?

(posted on Reddit: https://www.reddit.com/r/aws/comments/cq48vb/data_querying_searching_and_filtering_dynamodb/
stackoverflow: https://stackoverflow.com/questions/57493773/data-querying-searching-and-filtering-dynamodb-elasticsearch)

已提问 5 年前7293 查看次数
1 回答
0

Hey andrew-psch - This absolutely a good architecture pattern. AWS offers a diverse set of database services so you can pick the DB engine that best fits your use case. Here is a video of one of our SAs presenting on integrating DDB and Elasticsearch. https://www.youtube.com/watch?v=WXmghnE1_vU.

已回答 5 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则