I found https://www.lockss.org/use-lockss/how-lockss-works but it's really written for library/RDM types, not sysadmins/architects. https://github.com/lockss and https://docs.lockss.org/projects/manual/en/latest/introducti... don't obviously lead me to any papers on things like UBER, etc.
The reason I ask is because LOCKSS seems to take seriously the notion that data isn't really there unless you have checked it recently.
I found https://www.lockss.org/use-lockss/how-lockss-works but it's really written for library/RDM types, not sysadmins/architects. https://github.com/lockss and https://docs.lockss.org/projects/manual/en/latest/introducti... don't obviously lead me to any papers on things like UBER, etc.
The reason I ask is because LOCKSS seems to take seriously the notion that data isn't really there unless you have checked it recently.