Head of Development | Architect | 7x AWS Certified | AWS Community Builder | Serverless
An architect by trade, practicing architecture in the Cloud. 7x AWS Certified, AWS Community Builder, Serverless advocate, Vue enthusiast.
Markdown supported ยท โโต to post
Great to learn something! I'm new to DynamoDB and still confused why you prepended project# and monitor# to some GSIs, this would increase the redundancy and also unintentionally increase storage space.
Also, while querying, why do you query both, the primary key and the GSI, even though the schema says they contain the same data.
I might be totally getting the concept of GSIs wrong. Pardon me for that.
Thanks for the awesome and in-depth article ๐
Hey :)
Good article explaining the how, but I am left curious about the why :/
Why would you use a dynamoDB for relational data in lieu of just a relational database?
Stefan Olaru
Drew Davis
I wrote a npm package, dyna-record, which abstracts these design concepts. Iโm interested to know what you think of it. Iโm apparently not allowed to share links here but I wrote a blog title Unlock Relational Data Modeling in DynamoDB with dyna-record on medium