amazon s3 - Hbase on AWS EC2 -
i'm planning host website , want use hbase db. website photo sharing/hosting thing , not want use rdbms. want experience on hosting, learning hbase , issues faced , fixed web developers , backend designers.
in short, want create , host website in python + hbase purpose of learning them
i've experience ec2 , s3 , using aws infrastructure.
what i'm thinking of reserving:
- 3 default (1.7 g) instances hbase
- 3 more webserver + memcached if necessary
i want figure out if okay start with. of course, time, benchmarks, code optimisation , buy larger instances (if can afford them) if required.
as of now, above specs okay if targeted 1000 users?
the users viewing photographs or adding comments apart uploading pics. assume 1 user upoloads 20 photos per week on average.
i'm looking answers : "no, hbase can run in 1 medium size instance thousand users...." or "oh god 3 default servers 1000 users..."
1000 users total, or 1000 users concurrent? setup should fine 1000 users total.
as hbase on ec2: highly recommend running hbase on elastic map reduce (http://aws.typepad.com/aws/2012/06/apache-hbase-on-emr.html). doing way save hours having configure own ec2 clusters. believe me, i've done both ways , can't recommend emr approach enough. :)
Comments
Post a Comment