DynamoDB is great as you have summarised here. The problem I have in the industry is that not many people understand (or want to) that the "correct" way to use DynamoDB is a SINGLE database table as mush as possible. Then also you'll realise that there are already a proliferation of applications that do this the relational method of one-entity-per-table.
Also, not many like the "restriction" of knowing all your access patterns up front, which is quite important before you even start.
This information is I think a pre-requisite before you allow anyone near a DynamoDB database!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Awesome writeup!
DynamoDB is great as you have summarised here. The problem I have in the industry is that not many people understand (or want to) that the "correct" way to use DynamoDB is a SINGLE database table as mush as possible. Then also you'll realise that there are already a proliferation of applications that do this the relational method of one-entity-per-table.
Also, not many like the "restriction" of knowing all your access patterns up front, which is quite important before you even start.
This information is I think a pre-requisite before you allow anyone near a DynamoDB database!