1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
What is your usecase? Normally depending on the data retention requirement the number of partitions in a cluster is a good a indicator.
Check the best practises here: https://docs.aws.amazon.com/msk/latest/developerguide/bestpractices.html
Also you can check this blog for MSK serverless: https://aws.amazon.com/blogs/big-data/create-more-partitions-and-retain-data-for-longer-in-your-msk-serverless-clusters/
답변함 일 년 전
관련 콘텐츠
- AWS 공식업데이트됨 3년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전
Hi @rePost-User-2054795, here is the full use case:
Database of customer numbers ==>Adapter (any language) reading that 300K customer numbers once a month and posting one customer number at a time to a remote REST API and receives the response and storing the response in S3. How do we get this done efficiently considering the facts on throughput, data storage, latency, error handling, retry mechanism, data loss prevention, queues/topics, folder structure, cost and accomplish in few hours. I also want to use Amazon EKS in the same architecture. Can you help me out ?