Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Thx for the reply @JimmyJames. The ID that the api is referring to is the row-id, in my example - id345 (not user id, nor csv id). the user uploads a large db (as CSV) , and he wants a public api to get data about one specific row. How would you structure that? Commented Jan 21, 2020 at 11:35
  • @yonatanmn Ah, that changes things a good bit. I will need to revise my answer. You should probably clarify this distinction in your question. Another think that's important is the size of the rows. I major component of Dynamo pricing is done it terms of 'reads' and if I understand the pricing correctly, one read of 1K of data costs the same as a read of 4K of data. This leads me to the conclusion that lots of tiny records are not cost effective in Dynamo. Commented Jan 22, 2020 at 15:31