Amazon availability zones
I'm fairly new to Amazon services and wondering what some of the best
practices are for clustering/load balancing?
I have a load balancer in my colo (NJ) which may potentially be upgraded
to Netscaler.
The application we're hosting on Amazon is nothing crazy and don't expect
too much traffic. We're looking at 2 linux instances that would run a Node
JS application with a MongoDB replica set. From what I understand, Amazon
will evenly divide the traffic amongst the zones. The end-users location
has no effect on where they'll be distributed (ie if I have a server in
the west coast and one in the east coast, the user in the east coast could
be directed to either east or west).
If I wanted to direct users traffic based on location, a global DNS
solution would make more sense?
One server would be the master db and the other would be slave with data
replicating to each other.
Anybody have any experience with this and how is the network performance?
A question about EC2/S3
EC2 Instances and S3 buckets can only communicate if they are in the same
region, correct?
No comments:
Post a Comment