Nice article! Having used DynamoDB for some massive applications that first point really resonates - it feels like you need to put way too much effort into designing your data model to match your access patterns, and then that all goes out the window when your requirements change.

We've actually been building a new database that uses DynamoDB as an underlying storage layer but aims to address the lack of flexibility and difficulty in evolving your data model to meet new requirements: https://stately.cloud/blog/developers-should-be-able-to-chan... - we'd love feedback from folks who've been unsatisfied with DynamoDB.

Great article. I love DynamoDB but it is such a footgun. If you know how to work around the limitations + adhere to the Single Table design it's awesome.

But if you aren't familiar with it, you are destined to fail. I've seen so many poorly designed tables, with 10+ GSIs..