Rezultati pretraživanja
  1. 20. ruj 2017.

    The rest of my notes from the workshop with Including explanations about concurrency with cats 😸!

  2. 20. ruj 2017.

    Learning about fundamentals during our workshop with

  3. Prikaži ovu nit
  4. 29. ruj 2016.

    Most systems fail test. passed in v6.4. Not all vendors fix what finds, VoltDB does.

  5. 26. ožu 2019.

    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.

    Prikaži ovu nit
  6. prije 13 sati
  7. 26. tra 2016.

    How can someone be so bad at their job?

  8. 12. lip 2019.

    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:

  9. 11. velj 2016.

    Thanks for ! now that it passed, we'll contribute enhancements to it.

  10. 20. ruj 2017.

    Starting out our workshop with with an intro to ! 😍

  11. 5. ruj 2017.

    New analysis: the Tendermint blockchain system for byzantine fault tolerant replication of state machines:

    Prikaži ovu nit
  12. 5. ruj 2019.

    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.

    Prikaži ovu nit
  13. 16. velj 2017.

    Integrating ’s into our CI presented challenges, now protects us from regressions in linearizability:

  14. 6. lis 2017.

    In this analysis, we look at Hazelcast: an in-memory data grid with a habit of forgetting.

    Prikaži ovu nit
  15. 16. velj 2017.

    New analysis: reviewing and expanding 's tests. We found & fixed serializability violations!

  16. 1. ruj 2017.

    I've been experimenting with to check for application correctness, here's a writeup of where I got to & how:

    Prikaži ovu nit
  17. 9. velj 2016.

    RethinkDB 2.2.3: A rare case of split-brain after cluster reconfiguration

  18. 9. velj 2016.
  19. 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.

    Prikaži ovu nit
  20. 31. sij

    Reading posts is a 4 point story using the Fibonacci scoring

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.