5 ms·

Perhaps because FoundationDB is ACID compliant?

fweespeech 12y ago
Quorum Writes, Quorum Reads is as ACID compliant as FoundationDB iirc. The only thing I can think of is Apple has an internal team that is building a Cassandra replacement and they need more qualified engineers with experience.
- jhugg 12y ago
  Not even close. FDB did arbitrary multi-key transactions. Cassandra can only do Compare-And-Set on single keys IIRC.
jhugg 12y ago
So there is a point here. Apple is trying to compete with Google. Google has some amazing distributed systems, including Spanner, F1, MillWheel, etc... Apple has Cassandra and other OSS/COTS software. Not to ding Cassandra, but this is a problem for Apple. We've seen repeatedly that at huge scale, it often makes sense to own (or control) the software. See Facebook and LinkedIn as well. Now I don't think FDB (the product) is the answer, at least not in the short term. There are more problems scaling it to Apple's use case than there are working around Cassandra's lack of ACID. So I'm convinced the value of FDB is the experience in the engineers' brains. Apple need brains to run Cassandra, but also to figure out if Cassandra is the right long term path. Build, buy, adapt? It takes veterans to make the right call.
- threeseed 12y ago
  Apple runs Cassandra at scale today. It underpins most of iTunes Match and last time I checked all your iCloud data was sharded and stored in Cassandra. They run one of the latest clusters in the world (at least the last time I spoke with Datastax). Cassandra is a pretty easy database to run and scale and Datastax is just down the road from them to help. My guess is that FoundationDB is replacing their Teradata installation. Better to buy the company and invest heavily in it then let it not met it's full potential as a small startup.
threeseed 12y ago
Why do people think ACID is some panacea for every database problem ? It doesn't save you from data loss. It doesn't help you scale. It doesn't make it easier to manage. It doesn't actually help with 99% of the problems you typically experience with a database. A more measured, intelligent consideration of pros/cons is needed.
- carterehsmith 12y ago
  >> A more measured, intelligent consideration of pros/cons is needed. Every April 1st :)

Quorum Writes, Quorum Reads is as ACID compliant as FoundationDB iirc. The only thing I can think of is Apple has an internal team that is building a Cassandra replacement and they need more qualified engineers with experience.

jhugg 12y ago
Not even close. FDB did arbitrary multi-key transactions. Cassandra can only do Compare-And-Set on single keys IIRC.

jhugg 12y ago

So there is a point here. Apple is trying to compete with Google. Google has some amazing distributed systems, including Spanner, F1, MillWheel, etc... Apple has Cassandra and other OSS/COTS software. Not to ding Cassandra, but this is a problem for Apple. We've seen repeatedly that at huge scale, it often makes sense to own (or control) the software. See Facebook and LinkedIn as well. Now I don't think FDB (the product) is the answer, at least not in the short term. There are more problems scaling it to Apple's use case than there are working around Cassandra's lack of ACID. So I'm convinced the value of FDB is the experience in the engineers' brains. Apple need brains to run Cassandra, but also to figure out if Cassandra is the right long term path. Build, buy, adapt? It takes veterans to make the right call.

threeseed 12y ago
Apple runs Cassandra at scale today. It underpins most of iTunes Match and last time I checked all your iCloud data was sharded and stored in Cassandra. They run one of the latest clusters in the world (at least the last time I spoke with Datastax). Cassandra is a pretty easy database to run and scale and Datastax is just down the road from them to help. My guess is that FoundationDB is replacing their Teradata installation. Better to buy the company and invest heavily in it then let it not met it's full potential as a small startup.

threeseed 12y ago

Why do people think ACID is some panacea for every database problem ? It doesn't save you from data loss. It doesn't help you scale. It doesn't make it easier to manage. It doesn't actually help with 99% of the problems you typically experience with a database. A more measured, intelligent consideration of pros/cons is needed.

carterehsmith 12y ago
>> A more measured, intelligent consideration of pros/cons is needed. Every April 1st :)