My take is anything single cloud provider proprietary and tabular in 2025 is going to over time feel too limited. Having a json column doesn't cut it. But I'm a believer in document databases
Having a rigid and well-designed schema is a mechanism to keep you or your team from doing stupid things.
Cassandra et al. IMO only fall under the NoSQL banner by retconning the meaning to be “Not Only SQL.” Columnar DBs are a fine idea for certain uses.
Document DBs and/or chucking everything into a JSON column, though… those can die in a fire.
I am sorry but engaging in good faith, can you quality a little bit? Are you aware DynamoDB works as tier one product within AWS? Meaning it's one of the core pillars of the implementation of many other products?
Did you look at these references?: https://aws.amazon.com/dynamodb/customers/
Have you seen the real world use?: https://aws.amazon.com/blogs/aws/prime-day-2023-powered-by-a...
Before Spanner, Cockroach etc. for some workloads you didn't have alternatives but that time is long gone.