36 karma · joined July 11, 2016
What does transparent mean here? AWS is super clear what resources are zonal and provides tons of guidance around making things multi-AZ. AZ outages aren't exactly frequent but they're reasonably likely.
Being susceptible to AZ (or region) outages is very much an architectural decision. Or a bug that needs to be fixed (I'm sure Coinbase didn't YOLO single-AZ, they've undoubtedly learned about some edge case that needs to be fixed). Sure it may not be worth the cost/complexity for some systems but resiliency is like job one for anything in the cloud that costs money when it's down.
Replacing terms - that have been around so long that many systems' behaviors map to them closely - with new terms that don't quite overlap seems wildly more likely to create ambiguity and confusion.
Plus, relational databases don't just sit under a single application. There's usually multiple applications/services talking to them. Worse, humans connect to them an do all sorts of things they shouldn't do. That's the whole point of managing referential integrity in the DBMS, since you can only control "just write good code" across so many application domains.
Of course whether the performance tradeoff is worth it is a complicated decision for many of the reasons people have mentioned. But in 20 years of working with relational databases at big companies, I've seen few examples where the performance win exceeded the business risk.
(disclosure, I work for AWS)
[1] - BT just isn't great tech and there's odd interference/cutout, often around cars; open-case-near-phone-for-battery-level is clunky and inefficient; double-tap to play/pause (voice control for audio control is just non-sensical to me) often doesn't work if it's been more than a few minutes, and seems to prefer opening the Apple Music app which I never use