3 ms·
FoundationDB. Kyle didn't bother running Jepsen against FDB because foundationdb's internal testing was much more rigorous that Jepsen. The foundationdb team ra
by josephg 12y ago
FoundationDB. Kyle didn't bother running Jepsen against FDB because foundationdb's internal testing was much more rigorous that Jepsen. The foundationdb team ran it themselves and it passed with flying colors:
http://blog.foundationdb.com/call-me-maybe-foundationdb-vs-jepsen http://blog.foundationdb.com/call-me-maybe-foundationdb-vs-j...
Sadly, fdb has been bought by Apple[1], and you can't download it anymore. I sincerely hope foundationdb gets opensourced or something.
[1] http://techcrunch.com/2015/03/24/apple-acquires-durable-database-company-foundationdb/ http://techcrunch.com/2015/03/24/apple-acquires-durable-data...
- deleted 12y ago[deleted]
- timmaxw 12y agoActually, look at some of the things that @aphyr has tweeted about FoundationDB: https://twitter.com/aphyr/status/542792308492484608 https://twitter.com/aphyr/status/542792308492484608 https://twitter.com/obfuscurity/status/405016890306985984 https://twitter.com/obfuscurity/status/405016890306985984
- lobster_johnson 12y agoHe has said [1] that each test takes literally months to do. I am not surprised that he picks the most popular databases, given the amount of work. [1] https://github.com/rethinkdb/rethinkdb/issues/1493#issuecomment-47690227 https://github.com/rethinkdb/rethinkdb/issues/1493#issuecomm...
- takeda 12y agoI believe the real reason was that FDB was not open sourced. Jepsen tests cannot be used to prove the system is safe, but to prove it isn't. It looks like very often he looks into source code in order to figure out how the system operates, that way he can find weaknesses and write test to his testing framework to demonstrate the issue. I wouldn't trust any company that uses Jepsen to show that their product is safe.