Specifically: a globally visible distributed database is a fantastic resource for managing namespaces, as demonstrated by DNS and SSL Certificate Authorities.
But when we start essentially doing _transactions_ by writing into such a database, it starts to look like buying a domain name every time you want to make a credit card payment.
Tape. SQL databases emerged when data was stored on tape.
join table1, table2 where table1.id = table2.customer_id
type operations would have a tape for table1 in one drive, and a tape for table2 in the other drive. Things like fixed length records emerged to make it possible to fast forward the tape a specific number of inches to the point where the next record would begin, facilitating non-linear access.
Once that model was completely baked into the tooling, it didn't go away when the data moved to HDs then SSDs. The paradigms have outlived the hardware.
It's a bit like the save icon still being a floppy disk.
I've read a variety of reports. I've come to the conclusion that a bunch of weird shit went down, but that he did not have sex with anybody. The weird shit is well documented, and not that far from his claim of "testing his celibacy."
Bad there. 1000 times worse in India, relative to both Christianity and Islam, and with the great aggravating force of Yogi Adityanath pouring salt into those wounds.
I know of no framework to look at that question which isn't basically just a bunch more questions: in Scandinavia there are old pagan branches coming back up, Latvia too - but was the original tradition lost and they're neopagans, or was it alive on the farms and it's now coming back above the surface. It's like financial reparations: once you begin, where do you end?
I grew up in the West. I'm glad it's not my fight, I'd sweat hard finding a position!
But when we start essentially doing _transactions_ by writing into such a database, it starts to look like buying a domain name every time you want to make a credit card payment.
There is an architectural problem here.