wiki/amazon-ec2.md
... ...
@@ -251,11 +251,6 @@ Here are the steps to create a load balanced setup:
251 251
- Associate all your instances
252 252
- Connect your domain with the IP of the load balancer. It could be a good idea to use an Elastic IP that always stays the same for the domain and associate it with your load balancer. That way you can also easily switch between a load balancer and a single instance setup.
253 253
254
-Two things are still needed before this setup can be executed:
255
-
256
-- Make it possible to configure instances that way that they automatically connect to a master upon start
257
-- Check what happens if the ELB acts as a transparent proxy not revealing the underlying instance name and address (should be)
258
-
259 254
Amazon ELB is designed to handle unlimited concurrent requests per second with “gradually increasing” load pattern (although it's initial capacity is described to reach 20k requests/secs). It is not designed to handle heavy sudden spike of load or flash traffic because of it's internal structure where it needs to fire up more instances when load increases. ELB's can be pre-warmed though by writing to the AWS Support Team.
260 255
261 256
### Access MongoDB database