I see no mention of foreign keys, or any other constraints, across shards. If, as I suspect, they're not implemented, it would still be useful but at the level of Spanner 10 years ago.

▲

aabhay 4 hours ago | parent [-]

Cross shard transactions are “coming soon”. So, this is just like having multiple postgres clusters.

▲

spongeboi 4 hours ago | parent [-]

Cross shard transactions are supported, but we don't have support for atomic 2pc cross shard transactions, its WIP

	▲	ragall 29 minutes ago \| parent [-]
		Are you one of the developers ? If so, you need to add a specific page explaining in detail the guarantees that this gives. For example: point 08 says "Assign different tables or workloads to different shard groups" and point 02 says "Split hot shards as workloads grow". How do those interact ? Can a single table be split across multiple shards ? If so don't you need 2pc to enforce primary key constraints ? The intro pages just read as AI slop.