>6. Save your routing tables in memory, don't go fetch from DB on every 
request.
For now I'm query the db every time a request comes in. I tried keeping it 
in memory but i need to find a better way to push to all nodes in the 
cluster.

>7. Cluster + in memory state for apps, support nightmare
To scale out this is needed. In memory state for apps is something the 
developer would have to consider.

>8. Multi-port apps, don't do it unless you are letting people drop their 
own load balancers.
Drop their own load balancers is far fetch as the load balancing is a core 
part of raft.

Raft is very slimier to how heroku works in fact heroku has been 
a meager influence to raft. I need to do more reading about how heroku does 
scaling with their dynos.

I was thinking about multi request from the same user to different app. 
Maybe something like a session or by ip to route the same user to the same 
app every time. This would stop one request to one app and another request 
to the second app from the same user. This would help the developer to keep 
an in app state.

On Thursday, August 16, 2012 12:04:36 AM UTC-4, Bradley Meck wrote:
>
> When using multiple load balancers for multiple domains:
>
> 1. SNICallback in https is your friend for figuring out domains.
> 2. You will want to be grabbing data from a shared storage facility like a 
> Database where you can replicate down to your balancers. This information 
> will hold info on where to route requests, when to remove drones from the 
> tables, and even info such as load averages ideally.
> 3. RoundRobin works better than you might think #2 is overkill usually.
> 4. Use IP hashes to determine consistently where your connection/session 
> should go to, sending reconnect and session logic to 2 different drones can 
> lead to bad behavior.
> 5. Terminate SSL for the love of all that is holy if you have already 
> locked down your workers.
> 6. Save your routing tables in memory, don't go fetch from DB on every 
> request.
> 7. Cluster + in memory state for apps, support nightmare
> 8. Multi-port apps, don't do it unless you are letting people drop their 
> own load balancers.
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to