Twitter | Pretraživanje | |
Pretraživanje Osvježi
Joy Heron 20. ruj 2017.
The rest of my notes from the workshop with Including explanations about concurrency with cats 😸!
Reply Retweet Označi sa "sviđa mi se"
Joy Heron 20. ruj 2017.
Learning about fundamentals during our workshop with
Reply Retweet Označi sa "sviđa mi se"
Marist Volleyball 🏐 17. tra
IT’S OFFICIAL ✈️✈️✈️ ✍🏼🏐💯 🎥🎥
Reply Retweet Označi sa "sviđa mi se"
ann_dalrymple 29. ruj 2016.
Most systems fail test. passed in v6.4. Not all vendors fix what finds, VoltDB does.
Reply Retweet Označi sa "sviđa mi se"
Jepsen 26. ožu
In this analysis, we explore three safety bugs in DB: a distributed, multi-model database which combines sharded instances of Raft with leader leases, hybrid logical clocks, and a custom 2PC cross-shard transactional protocol.
Reply Retweet Označi sa "sviđa mi se"
Hazelcast 13 h
Reply Retweet Označi sa "sviđa mi se"
Zach Chivers 26. tra 2016.
How can someone be so bad at their job?
Reply Retweet Označi sa "sviđa mi se"
Jepsen 12. lip
In the latest analysis, we worked with to test TiDB 2.1.7 through 3.0.0-rc.2. Due to 2 transaction retry mechanisms, TiDB exhibited constant snapshot isolation anomalies under normal conditions. This and other bugs are fixed in 3.0.0-rc.2:
Reply Retweet Označi sa "sviđa mi se"
Scylla 11. velj 2016.
Thanks for ! now that it passed, we'll contribute enhancements to it.
Reply Retweet Označi sa "sviđa mi se"
Joy Heron 20. ruj 2017.
Starting out our workshop with with an intro to ! 😍
Reply Retweet Označi sa "sviđa mi se"
Yukon Whorenelius 5. ruj 2017.
New analysis: the Tendermint blockchain system for byzantine fault tolerant replication of state machines:
Reply Retweet Označi sa "sviđa mi se"
Jepsen 5. ruj
New report! We worked with to evaluate YugaByte DB 1.3.1's beta support for serializable SQL transactions. We found 2 safety bugs including anti-dependency cycles (now fixed), and availability issues like a slow leak in backend processes.
Reply Retweet Označi sa "sviđa mi se"
MongoDB Engineering 16. velj 2017.
Integrating ’s into our CI presented challenges, now protects us from regressions in linearizability:
Reply Retweet Označi sa "sviđa mi se"
Yukon Whorenelius 6. lis 2017.
In this analysis, we look at Hazelcast: an in-memory data grid with a habit of forgetting.
Reply Retweet Označi sa "sviđa mi se"
Yukon Whorenelius 16. velj 2017.
New analysis: reviewing and expanding 's tests. We found & fixed serializability violations!
Reply Retweet Označi sa "sviđa mi se"
Caligin Tsukihara 1. ruj 2017.
I've been experimenting with to check for application correctness, here's a writeup of where I got to & how:
Reply Retweet Označi sa "sviđa mi se"
Yukon Whorenelius 9. velj 2016.
RethinkDB 2.2.3: A rare case of split-brain after cluster reconfiguration
Reply Retweet Označi sa "sviđa mi se"
Alex 9. velj 2016.
Interesting insights on how uses for testing:
Reply Retweet Označi sa "sviđa mi se"
Yukon Whorenelius 7. ožu 2018.
In the latest analysis, we return to 3.99.0.3, checking their next-generation consensus system scheduled to be released in 4.0. We confirm data loss due to process crashes and 27+ second pauses, and found a subtle bug in proxied nacks.
Reply Retweet Označi sa "sviđa mi se"
Jaryd Remillard 31. sij
Reading posts is a 4 point story using the Fibonacci scoring
Reply Retweet Označi sa "sviđa mi se"