What is the backup / restore story in FoundationDB? How does it compare to postgresql?
FoundationDB: A distributed, unbundled, transactional key value store [pdf]
31–40 of 103 posts
Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#32Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#33Here's one of my favorite articles on FoundationDB, where it (FDB) passes Jepsen first try: https://web.archive.org/web/20150312112556/http://blog.found... > I ran FoundationDB Key-Value Store through every nemesis in Jepsen - including those that found failures in other databases - and FoundationDB passed all of them with flying colors. FoundationDB is one of the coolest pieces of technology I've used in the past de…
Having someone other than those officially on the Jepsen project run the Jepsen test is a good start. However, many databases have claimed to run the Jepsen tests themselves and pass, but when there is an actual paid engagement for a distributed database there are always issues that are found. That's generally true even for unpaid official runs as well although Zookeeper did pass existing tests. Every database is different and the paid engagement will design specific tests designed to break the database in question.
Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#34We run several FDB clusters using 3-DC replication and have never once lost data. I remember when we wanted to replace all of the FDB hardware (one cluster) in AWS, and so we just doubled the cluster size, waited for data shuffling to calm down, and just started axing the original hardware. We did this all while performing over 100K production TPS.
One thing that makes the above seamless for all existing connections is that clients automatically update their "cluster file" in the event that new coordinators join or are reassigned. That alone is amazing...as you don't have to track down every single client and change / re-roll with new connection parameters.
Anyway, I talk this database up every chance I get. Keep up the awesome work.
- A very happy user.
Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#35Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#36Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#37Two quotes from the paper that I think will motivate people to read it: "Rigorous correctness testing via simulation makes FDB extremely reliable. In the past several years, CloudKit [59] has deployed FDB for more than 0.5M disk years without a single data corruption event. Additionally, we constantly perform data consistency checks by comparing replicas of data records and making sure they are the same. To this date…
> de novo Paxos implementation written in Flow That's... brave. Flow is a DSL built on top of C++?
Their talk from a while ago about it was something that really blew me away at the time [0]
Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#38Here's one of my favorite articles on FoundationDB, where it (FDB) passes Jepsen first try: https://web.archive.org/web/20150312112556/http://blog.found... > I ran FoundationDB Key-Value Store through every nemesis in Jepsen - including those that found failures in other databases - and FoundationDB passed all of them with flying colors. FoundationDB is one of the coolest pieces of technology I've used in the past de…
Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#39FDB is an awesome and unique piece of software (I attribute quite a bit of Snowflake's success to FDB). I've also had the pleasure of meeting some folks from the original team and they are true engineers. Does anyone know if/when Redwood (the new storage engine) has landed / will land?
Re: FoundationDB: A distributed, unbundled, transactional key value store [pdf]
#40They got acquihired by apple, didn't they? Was. Fdb ever oss'd? Is it CP or AP? Comments seem to imply AP