It's pretty heavily used within Azure itself, and my old team didn't have any issues, even though we had a high volume service with stored procs, triggers, list indexes, etc. And it was cheaper and faster than the SQL Server instance it replaced (granted, the original Sql-based app had tons of big joins and wasn't designed to scale).
I know a few other teams when I was working elsewhere that had to migrate off Spanner due to throttling and random hiccups, though if Google uses it for zanzibar, they must not have that problem internally. Maybe all these companies increase throttling limits for first party use cases.
My current team uses dynamo, which has also given throttling issues, but generally only when they try to do things that it's not designed for (bulk updating a bunch of records in the same partition). Other than that, it seems reliable (incredibly consistent low latencies) and a bit cheaper than my experience with cosmos, though with fewer features.
They all seem to have their own pros and cons in my experience.
I know a few other teams when I was working elsewhere that had to migrate off Spanner due to throttling and random hiccups, though if Google uses it for zanzibar, they must not have that problem internally. Maybe all these companies increase throttling limits for first party use cases.
My current team uses dynamo, which has also given throttling issues, but generally only when they try to do things that it's not designed for (bulk updating a bunch of records in the same partition). Other than that, it seems reliable (incredibly consistent low latencies) and a bit cheaper than my experience with cosmos, though with fewer features.
They all seem to have their own pros and cons in my experience.