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년 전2485회 조회
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년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠