Design Pattern for daily upload of source data i(in graphql) into dynamo

0

Hello I am looking for best practices in designing a simple solution to retrieve a large data set (100K orders) daily into a dynamo DB.

At the moment, the source data (orders) is accessible via graphql api , but the solution needs to cover other methods, such as as REST API.

Also, I need something configurable the data sources object model evolve on a regular base.

In the old days of EAI, we would simply use an out of the box configurable adapter (usually with object mapping wizards) for mapping source object modes (at data field level) to target object data model. Just wondering what the AWS best practices for this scenario? thanks a lot :)

질문됨 일 년 전218회 조회
1개 답변
0

Hello, Based on your query, I do believe that you could try leveraging the AWS Architecture Center, that offers reference architecture diagrams, vetted architecture solutions, Well-Architected best practices, etc.

Nevertheless, in case you are seeking guidance specific to your use case, please feel free to get in touch with an AWS Solution Architect who have the right expertise with multiple AWS Services and can assist you. You can fill up this contact form (Nature of Support - Sales Support) and an AWS SA from the team will get back to you on the same.

AWS
지원 엔지니어
답변함 일 년 전

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

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

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

관련 콘텐츠