Isn't Availablility the ability to connect to something? If I'm calling from region A to region A servers, and the region A servers' networks go down. Well, my client is clever and can failover to region B servers. Except, all my state and context was on region A servers, and maybe that state wasn't replicated over to region B - that replication might only happen on a nightly basis.

When I reconnect, my dating profile is missing all the pictures I uploaded of me in my new convertible with me lowering my sunglasses and winking at the camera.

The LovinHuggin.com server architecture is Available, but not Partition Tolerant. And after I upload different pictures of me in tuxedos and talking like a boss on the cellphone to region B, I've potentially created a weird "split brain" situation. Region A and region B servers have different views of me. Both views are super hot, but the client might get confused if my session returns to region A when their network heals, and the nightly region replication might be messy with reconciling the split brain. Eventual consistency is a helpful (or fraught) feature to have in the database when things like split brain happen.