About pricing, it is interesting how caching is apparently not an effective option to reduce the bill in a significant way since data size is a big component of price.
Thats because it is SSD based, so size starts to matter again.
A Tour of Amazon's DynamoDB
21–30 of 32 posts
Re: A Tour of Amazon's DynamoDB
#22I would second Mathias' thoughts in that this does feel more bigtable/column oriented than traditional dynamo. Dynamo and its derivative, Riak (not from amazon), make no attempt to determine data types or schema in any way. The fact that dynamodb can do range scans and has various counting features leads me to believe that it is more hybridized along the lines of Cassandra. Either way, it is a welcome addition to the nosql toolset that developers have to chose from today. I will certainly look at it more closely.
Re: A Tour of Amazon's DynamoDB
#23I would second Mathias' thoughts in that this does feel more bigtable/column oriented than traditional dynamo. Dynamo and its derivative, Riak (not from amazon), make no attempt to determine data types or schema in any way. The fact that dynamodb can do range scans and has various counting features leads me to believe that it is more hybridized along the lines of Cassandra. Either way, it is a welcome addition to the…
Actually Riak can be used in a way in which it is content-aware of JSON and XML documents.
http://wiki.basho.com/Riak-Search---Indexing-and-Querying-Ri...
Re: A Tour of Amazon's DynamoDB
#24About pricing, it is interesting how caching is apparently not an effective option to reduce the bill in a significant way since data size is a big component of price.
Thats because it is SSD based, so size starts to matter again.
Yes but real hardware with an SSD disk plugged inside could deliver excellent performances with many reasonable on-disk databases, with a fraction of the cost per megabyte, with many many millions of keys.
It is like that other than the fact you don't have to manage the DB, that is a good point, here the best reason for many small-mid business to use such a service is since they are already on EC2. May work in the short term but I see something odd about this model.
Re: A Tour of Amazon's DynamoDB
#25I would second Mathias' thoughts in that this does feel more bigtable/column oriented than traditional dynamo. Dynamo and its derivative, Riak (not from amazon), make no attempt to determine data types or schema in any way. The fact that dynamodb can do range scans and has various counting features leads me to believe that it is more hybridized along the lines of Cassandra. Either way, it is a welcome addition to the…
Actually Riak can be used in a way in which it is content-aware of JSON and XML documents. http://wiki.basho.com/Riak-Search---Indexing-and-Querying-Ri...
Search and Indexing were addons to the initial Riak product that were born from user demand. Only recently (1.0 I believe) was Search integrated into the main Riak distribution. Riak has no capability of updating values in place, ie. a partial update and no means of ordering or pagination. Some of these features are available via mapreduce queries or Search/Index as you noted.
I'm by no means harping on Riak. I actually use it on a number of projects. But reading about DynamoDB's capabilities does not conjure Riak, it conjures Cassandra and HBase.
Re: A Tour of Amazon's DynamoDB
#26Earlier quoted context omitted.
Actually Riak can be used in a way in which it is content-aware of JSON and XML documents. http://wiki.basho.com/Riak-Search---Indexing-and-Querying-Ri...
Search and Indexing were addons to the initial Riak product that were born from user demand. Only recently (1.0 I believe) was Search integrated into the main Riak distribution. Riak has no capability of updating values in place, ie. a partial update and no means of ordering or pagination. Some of these features are available via mapreduce queries or Search/Index as you noted. I'm by no means harping on Riak. I actua…
I agree with you on other counts, but Riak is a far cry from the spartan implementation of Dynamo outlined in the paper.
Re: A Tour of Amazon's DynamoDB
#27The API doesn't bother me as much as the temporary authentication via STS. Temporary credentials for database access? Seriously? I am the only one who sees how ridiculous this is?
What's wrong with using temporary credentials?
Re: A Tour of Amazon's DynamoDB
#28DynamoDB 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.
[deleted]
Re: A Tour of Amazon's DynamoDB
#29I'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
I'm struck by how you somehow manage to pimp both Cassandra and DataStax on every post which has something to do with databases and/or datastores. :)
Re: A Tour of Amazon's DynamoDB
#30The API doesn't bother me as much as the temporary authentication via STS. Temporary credentials for database access? Seriously? I am the only one who sees how ridiculous this is?
What's wrong with using temporary credentials?
They add useless latency and another point of failure. And sometimes, the AWS APIs DO fail.