11–20 of 32 posts
I'm still struck by what a strong endorsement DynamoDB is of the design decisions we've been making in Cassandra over the last couple years. Composite keys, distributed counters, ... More details: http://www.datastax.com/dev/blog/amazon-dynamodb
Both projects seem to be moving so quickly that it's really hard to find an up to date comparison.
Does anyone know in which language DynamoDB is implemented? I've read somewhere that SimpleDB is done in Erlang. Is that the case with DynamoDB as well? I've been reading about Ets and Dets in Erlang and it makes me wonder whether they have anything to do with either of these data stores.
{"__type":"com.amazon.coral.validate#ValidationException",
"message":"One or more parameter values were invalid:
The provided key size does not match with that of the schema"}DynamoDB is not open source, at least according to a blog comment by Jeff Barr of AWS. ( http://aws.typepad.com/aws/2012/01/amazon-dynamodb-internet-... ) I'm certainly not going to commit to platform lock-in like that. I know a lot of folks were hit hard by Googles app engine price changes and it could happen again here with DynamoDB.
DynamoDB is not open source, at least according to a blog comment by Jeff Barr of AWS. ( http://aws.typepad.com/aws/2012/01/amazon-dynamodb-internet-... ) I'm certainly not going to commit to platform lock-in like that. I know a lot of folks were hit hard by Googles app engine price changes and it could happen again here with DynamoDB.
Then you don't use S3?
DynamoDB is not open source, at least according to a blog comment by Jeff Barr of AWS. ( http://aws.typepad.com/aws/2012/01/amazon-dynamodb-internet-... ) I'm certainly not going to commit to platform lock-in like that. I know a lot of folks were hit hard by Googles app engine price changes and it could happen again here with DynamoDB.
Then you don't use S3?
Also, the risk of S3 pricing changing greatly is constrained by the wide adoption. If DynamoDB failed to become pervasive, it would be relatively easy for Amazon to increase the price to make an underutilized service profitable. OTOH, if DynamoDB does become as popular as S3 your exposure to risk will be much less.
Earlier quoted context omitted.
Then you don't use S3?
I don't actually, but I feel there is less lock-in. It wouldn't be hard to move off. Also, the risk of S3 pricing changing greatly is constrained by the wide adoption. If DynamoDB failed to become pervasive, it would be relatively easy for Amazon to increase the price to make an underutilized service profitable. OTOH, if DynamoDB does become as popular as S3 your exposure to risk will be much less.
I'm still struck by what a strong endorsement DynamoDB is of the design decisions we've been making in Cassandra over the last couple years. Composite keys, distributed counters, ... More details: http://www.datastax.com/dev/blog/amazon-dynamodb
Facebook took up the Dynamo torch and created Cassandra... then switched to HBase after trying to use Cassandra in production.
Have you ever stopped to wonder about what Amazon might have taken OUT of Dynamo before launching DynamoDB? Things that Cassandra still has and just might be holding it back?
That to me seems much more important than just saying "DynamoDB has feature X that Cassandra has had for years! We're so smart!"
I've been waiting for Mathias to write something like this, and I'm glad he didn't waste any time diving in. For those who don't know him, he has more breadth in the area of emerging datastores than anyone I know; he literally wrote the book on Riak[1]. I've also been acquainting myself with the DynamoDB API over the past week, and am building a node.js binding that I hope will abstract away most of the esoteric aspe…
I'm still struck by what a strong endorsement DynamoDB is of the design decisions we've been making in Cassandra over the last couple years. Composite keys, distributed counters, ... More details: http://www.datastax.com/dev/blog/amazon-dynamodb
Dynamo as described in the original paper was not made into a web service. Facebook took up the Dynamo torch and created Cassandra... then switched to HBase after trying to use Cassandra in production. Have you ever stopped to wonder about what Amazon might have taken OUT of Dynamo before launching DynamoDB? Things that Cassandra still has and just might be holding it back? That to me seems much more important than j…
The original Dynamo was plain key/value with O(1) routing and vector clocks; there's not much else to strip out. :)
P.S. Facebook built Messages on HBase instead of Cassandra for political reasons rather than technical, and shards HBase to mitigate the availability problems it has otherwise. Facebook never ran an Apache Cassandra release in production.