My Disappointments with Amazon DynamoDB | WhyNosql
I was really excited with Amazon's DynamoDB annoucement. After developing for few days with it and using it in production, I was a bit disappointed.
Many of those disappointments come from comparing our existing HBase with DynamoDB. After this evaluation, we think that we simply cannot replace our HBase installation. We can use DynamoDB for some other lightweight applications.
1) 64KB limit on row size: We have many records in our HBase with data much more than 64KB in one row. We even had some records as big as 100MB. Limiting row size to such a tiny amounts rules out lots of use cases for us instantly. In one of the user forum threads here is what one of the Amazon guys say about the limit :
"64KB cumulative attribute size limit, which isn't too hard to reach if you have a set of Number values for a single attribute When you have so many values for a set, you should consider switching your table to a hash-range schema."
I think what he is missing is that there could be genuine cases where switching your table to hash range schema may not be possible. In some cases single piece of data is bigger than 64KB. You cannot simply change your schema to use more rows instead of more columns in these cases. For example a page crawler may store the entire page content in one field. Somebody might want to store an Image as a field in your NoSQL database. You simply cannot use DynamoDB for such use cases. This is my biggest complaint.
Read full article from My Disappointments with Amazon DynamoDB | WhyNosql
No comments:
Post a Comment