Pinboard (jm)
https://pinboard.in/u:jm/public/
recent bookmarks from jmCall me maybe: Aerospike2015-05-05T22:17:45+00:00
https://aphyr.com/posts/324-call-me-maybe-aerospike
jmaerospike outages cap testing jepsen aphyr databases storage reliabilityhttps://pinboard.in/https://pinboard.in/u:jm/b:4d9d3218df60/Call me maybe: Elasticsearch 1.5.02015-05-04T22:57:52+00:00
https://aphyr.com/posts/323-call-me-maybe-elasticsearch-1-5-0
jmelasticsearch reliability data storage safety jepsen testing aphyr partition network-partitions caphttps://pinboard.in/https://pinboard.in/u:jm/b:b6fc5795a3e6/Good advice on running large-scale database stress tests2014-12-11T14:19:12+00:00
https://twitter.com/aphyr/statuses/542779934851072000
jmbiebermark benchmarks testing performance stress-tests databases storage mongodb innodb foundationdb aphyr measurement distributions keys zipfianhttps://pinboard.in/https://pinboard.in/u:jm/b:9fb30019be5a/Aerospike's CA boast gets a thumbs-down from @aphyr2014-09-09T09:43:24+00:00
https://twitter.com/aphyr/statuses/509104476976717825
jmSpecifically, @aerospikedb cannot offer cursor stability, repeatable read, snapshot isolation, or any flavor of serializability.
@nasav @aerospikedb At *best* you can offer Read Committed, which is not, I assert, what most people would expect from an "ACID" database.
]]>aphyr aerospike availability consistency acid transactions distcomp databases storagehttps://pinboard.in/https://pinboard.in/u:jm/b:874bcb9ed3ec/