21–30 of 70 posts
Earlier quoted context omitted.
Haven't you noticed the pedigree obsession of some in our field?
In this context it adds more signal than noise. There are zillions of open source projects but when you need to use them in production a very small subset of this universe is ready.
Here in the Southeast, we call them "Palmetto Bugs". Maybe a rename to PalmettoDB? :)
Are there distributed data stores like this that are also resilient to intentional sabotage? I've been looking recently at long-term digital preservation systems -- tools designed to archive large amounts of data for decades. This is the Library of Alexandria problem -- how do we preserve all this data we're generating against once-in-a-century disasters? So this 2005 paper lists thirteen different threats to long-te…
I guess you're asking whether there exists a distributed fault-tolerant with a form of version control (similar to git/cvs/perforce) as part of the native feature set.
MySQL: Weak consistency
Cassandra: No availability or weak consistency with datacenter failure
So I cannot tell if this is aiming to be CA or AP. Having beaten my head against the CAP wall for a while, how does it deal with partitions?
Are there distributed data stores like this that are also resilient to intentional sabotage? I've been looking recently at long-term digital preservation systems -- tools designed to archive large amounts of data for decades. This is the Library of Alexandria problem -- how do we preserve all this data we're generating against once-in-a-century disasters? So this 2005 paper lists thirteen different threats to long-te…
Well, Git has checksums on everything.
Earlier quoted context omitted.
In this context it adds more signal than noise. There are zillions of open source projects but when you need to use them in production a very small subset of this universe is ready.
Does it? I don't think ex-Googlers gives anything of value here.