Because a key-value store is a foundamentally simpler data structure (it's an hash) than a relational database, which tracks the relations between different data types. If you make an advanced use of the key-value store, you have a lot of logic in the application (for example to key management, cascade operations between related data...) which a relational database should do for you. It's not fair because there is a development cost in using the key-value you are ignoring.
DDB -> NoSQL, No Automatic backups, No support for ad-hoc querying, eventual consistency (though you can set to get consistency with few tradeoffs)
Spanner DB -> RDBMS, Automatic backups, Enriched SQL, Strong consistency.
Let me if you still think its fair to compare these 2 databases.
Sounds like you're either not that big or you have an incompetent team. If you have PCI/HIPAA/whatever under control, it doesn't magically get harder as you get bigger. Outsourcing it just means you pay someone else to get it right, in addition to giving up control.
People really need to stop. There is no Fortune 15. I get that your e-peen needs all the help it can get, but this is like a grown adult giving their age as 41 "and 3 quarters".
What others? At this point you seem to be just naming things. containerd and runc are both parts of Docker, and OpenShift is a PaaS that runs on Docker.