Thanks for the article !
I was wondering, any reason you didn t consider Aurora for RDB instead of Dynamo ? I guess it s a bit harder to adapt code to match the limitations of DynamoDB for regular APIs
Aurora is a part of RDS so I didn't mention the name. The reason why I didn't pick Aurora is same as mentioned in the article, cost(I don't want to pay fixed charge), agility(I don't want tables depended each other), development speed.
But as you say, DynamoDB has limitations and it would be critical for some requirements. We should consider requirements and design of data model.
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.
Thanks for the article !
I was wondering, any reason you didn t consider Aurora for RDB instead of Dynamo ? I guess it s a bit harder to adapt code to match the limitations of DynamoDB for regular APIs
Aurora is a part of RDS so I didn't mention the name. The reason why I didn't pick Aurora is same as mentioned in the article, cost(I don't want to pay fixed charge), agility(I don't want tables depended each other), development speed.
But as you say, DynamoDB has limitations and it would be critical for some requirements. We should consider requirements and design of data model.