1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
2
First, to pricing: Look at the on-demand pricing page for DynamoDB. The first 25 GB of storage is free; and the read/write requests are very low cost so you might only end up spending cents depending on your usage. You can also see from the free tier page that this is perpetual - not just for the first year.
Second to the database design - some tips that I've learned the hard way over the years:
- With DynamoDB the structure is completely up to you and the best way to think about it is as a de-normalised database. That is, you might end up repeating a bunch of data but it's cheaper to store and retrieve that way even if it seems inefficient compared to a relational database.
- That brings the challenge of querying the database: Pulling a record back out based on a unique identifier is extremely fast and very inexpensive. But scanning the table for (say) "all records on a particular date" can be "expensive" in terms of the amount of data that has to be read in order to satisfy the query and that can also lead to higher charges.
- Therefore, consider carefully how you want to retrieve the data. If you just want to bring things back based on date that's totally fine; but you'll also need some other uniqueness in there to select which record from that date you want.
- You can always add indexes to make querying simpler; but those add to the cost of the database table. It might be more cost effective to use a different schema instead. Don't be afraid (especially with the amount of data that you have) to just "start again".
Finally, there are many guides on the internet about how to design a schema. Start here and then experiment.
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 3년 전
- AWS 공식업데이트됨 8달 전