I'm looking for advice on setting up load balancing for a web application I'm building. I'm looking to use at least 2 web front ends and want to know where to start.
Should I just use DNS load balancing with a service like Amazon Route 53? Do I need a dedicated instance to serve as a load balancer?
I realize the answer likely depends on the amount and type of traffic I expect to have, but are there rules of thumb I can use to get started? Thanks in advance.
I was under the impression route 53 is just a dns server/service. A good place to start is to program your app for dual core processor: java e.g. Made this easier by introducing threads: you send certain commands to one core and others to the other. It helps to get your mind around how you want to set up your app and where to queue events
Jan Vladimir Mostert
Idea Incubator
AWS has something called Elastic Load Balancing which can balance load between healthy instances, so no, you don't need a separate instance for the load balancer unless you plan on running your own load balancer like NGINX.
DNS load balancing is probably overkill, you can easily add that later on if needed. Ideally, you'd setup your domain to point to your load balancer and the load balancer will swing traffic between instances.