Is it necessary to use a strongly consistent transactional data store if your needs don't demand transactions, by transactions I mean 2PC. IMO you are still better off with DynamoDB/Cosmos/MongoDB for eventual consistency use cases. The reason being, you have to resort to a data model if you don't need the relational layer in YugaByte at least, not sure about Spanner. So why bother with Yugabyte if am resorting to a data model. Might as well stick with DynamoDB.
And technically all relational databases are relational layers on top of a key/value subsystem. Splitting that apart and scaling the storage is how most of the NewSQL databases scale , from CRDB to Yugabyte to Neon.
Of course, every data store needs a data model. No debate there :).
Not sure what you mean by relational databases are relational layers on top of key-value stores. InnoDB has a 16KB page data as it's fundamental data structure.
https://dev.mysql.com/doc/internals/en/innodb-page-structure...
Suggests there may be an impossibility theory lurking somewhere.
[1] https://cwiki.apache.org/confluence/download/attachments/188...
Like Cassandra, dynamodb requires the data model to be designed very carefully to be able to get the max out of them.
More often than not, that simply adds more complexity; people often underestimate how much a sharded mysql/Postgres can scale.
My default choice for the longest time: Postgres for the data I care about, ES as secondary index and S3 as blob storage.