What's your take on Aurora DSQL?

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

Relational databases (sans JSON columns) are limited in the same way that seatbelts limit your ability to be transfenestrated during a crash.

Having a rigid and well-designed schema is a mechanism to keep you or your team from doing stupid things.

nosql does not imply no schema

I think most would infer that, but in any case, it most definitely implies a non-rigid schema.

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.

the only thing nosql means is that there are no relations. mongodb 8 and newer for example support schemas and validations, cascading checks, etc. dynamodb, more relevantly does also support a schema, and in fact you can't even create a table without defining one.

Honestly haven't really had to deal with use case where json column does not cut it, but I would imaging there might be some.

> AWS needs to buy a proper newSQL databse Dynamo is just horribly outdated product.

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...

very low limit on number of keys in transaction very low limit on ops/sec on a single key extremely cumbersome to change the data layout development experience is just abysmal

Before Spanner, Cockroach etc. for some workloads you didn't have alternatives but that time is long gone.