I feel the integrity of data is WAY more important than pure performance and scalability. This is why i always shunned planetscale [vitess] (make no mistake, i really like their product and they have a nice free tier). When the need for sharding comes you have probably "made it" and most likely can afford a deeper refactor both in application and database design.
That said, true FK support is a very nice addition. However it really pains me to you MySQL, as it has a baggage it carries and is not SQL compliant. Thats why i always go for Postgres instead.
That said, true FK support is a very nice addition. However it really pains me to you MySQL, as it has a baggage it carries and is not SQL compliant. Thats why i always go for Postgres instead.