DSQL has some serious limitations (transaction size, but also others). I would say working with it feels more like Dynamo than Postgres.
Which is fine - it is a specialized system designed for specialized problems, not a drop in replacement for Postgres that would make your application magically multi-region.
Also, I'm not sure if it actually solves any scaling bottlenecks. Any distributed system that needs to reach consensus will be as slow or slower than single node, which does not need to do it. Yes, usual implementations only go through consensus for writing and reading isn't constrained ... but you can already do that with read-only replica of a normal database.
I feel like a lot of the trade-offs forced on you by dsql, you are forced into when scaling Postgres.
Like if I’m an SRE/DBA and you running massive update queries in a single transaction, that is the first thing I’m getting rid of.
I agree, same for foreign keys, triggers, higher isolation levels, the list goes on