I'm curious of a common situation. Could RDBMS be improved on that area, or do they inherently lack some necessary property?
I will agree that current RDBMS tend to lack dynamism, and that should be remedied: https://www.reddit.com/r/CRUDology/comments/12ari2l/dynamic_...
As for features I mean you could use Postgres and some extensions and you’re good to go. If you want a document db you can just use jsonb type.
You need to know your access patterns and what queries you will be running beforehand when working with something like dynamo. You can also do relational modeling with dynamo following single table design and basically pre join.
Obviously! "level up" does not imply you used the wrong thing on purpose and you're switching to another solution that's better in every way, as you seem to have read it.
Use the right tool for the right job.
I’ve migrated rdbms to wide column databases like Cassandra or dynamo because we had specific requirements that rdbms were not fulfilling.
I’ve also migrated from document database to rdbms because the document store didn’t meet our specific requirements.
I wouldn’t just use any random database because I want to appear cool (?) because I know Cassandra or how to use a vector database. That’s not the point.