How do you guys Load-balance over 2 apps? are you monitoring the apps load? 
or is it like the cluster module does it with round ribbon or what ever its 
called?

On Wednesday, August 15, 2012 5:40:52 PM UTC-4, jesusabdullah wrote:
>
> > Do you have more than one Haibu server running? 
>
> Yes. Dedicated apps each get their own haibu server. Meaning we're 
> running thousands of 'em. 
>
> > how would you go about doing ReverseProxy/LoadBalancing? 
>
> We use https://github.com/nodejitsu/node-http-proxy in our balancers. 
>
> --Josh 
>
> On Wed, Aug 15, 2012 at 2:30 PM, Gustavo Machado 
> <[email protected]<javascript:>> 
> wrote: 
> > Nodejitsu/Haibu guys, 
> > 
> > Do you have more than one Haibu server running? And if so, how would 
> > you go about doing ReverseProxy/LoadBalancing? 
> > 
> > Thanks, 
> > Gustavo Machado 
> > 
> > On Mon, Aug 13, 2012 at 2:03 PM, chrismatthieu 
> > <[email protected] <javascript:>> wrote: 
> >> Hi Tim, 
> >> 
> >> I'm the founder of Nodester, the open source Node.JS PaaS.  Your 
> project 
> >> sounds really cool!  Answers to your questions are provided below: 
> >> 
> >> - I know that nodester is hosted on AWS's and with that how many apps 
> are 
> >> hosted per server? Are the server like a 8GB/RAM 4/core pc running 
> maybe 20 
> >> apps per server, or is is a micro server running just one app? 
> >> 
> >> Nodester is currently hosting over 6,000 Node.JS apps on a single Extra 
> >> Large AWS instance without a reverse proxy!  We have a team currently 
> >> working on horizontal scaling and monitoring and the ability to spin up 
> >> additional resources like Heroku's dynos.  We are calling them "Jets" 
> to go 
> >> along with our rocket theme ;) 
> >> 
> >> - To nodester. why did you chose git for the pushing of apps to the 
> backend? 
> >> 
> >> We love Git!  It's the modern way for updating code and pushing updates 
> on 
> >> many services.  Now that Windows users are becoming more familiar with 
> git, 
> >> our support efforts have decreased with trying to teach people how to 
> use 
> >> it.  Setting up an RSA key the first time for git has always been our 
> most 
> >> FAQ.  Over time, this has proven to be the right decision! 
> >> 
> >> - To nodester / nodejitsu. Have you guys thought of a kind of dynos 
> (heroku 
> >> style)? if so how would you guys go about doing that? like you spawn 2 
> >> processes of the same app and just route request to each app like node 
> does 
> >> with the cluster module? 
> >> 
> >> Jets are coming... 
> >> 
> >> - To nodester. On average what are your costs running 3000+ app on 
> AWS's? 
> >> 
> >> $500 per month (which is sponsored by @Tropo) :) 
> >> 
> >> Gotta love the Node.JS community and Tropo - http://tropo.com! 
> >> 
> >> Hack the Planet! 
> >> @ChrisMatthieu 
> >> 
> >> 
> >> 
> >> On Saturday, August 11, 2012 2:33:21 PM UTC-7, Tim Dickinson wrote: 
> >>> 
> >>> Hey all. 
> >>> 
> >>> So this is not a ANN but more of an request for advice from nodester / 
> >>> nodejitsu / haibu and the community in general. What i have been 
> working on 
> >>> for the past few months is of sort a PaaS. The basic idea behind it is 
> to 
> >>> create a server to can spawn node apps that are pushed out to it with 
> a cli. 
> >>> 
> >>> I'm calling it Raft as in a boat to float apps on. It has gone through 
> a 
> >>> few iterations since it creation. It started out as a MVC style app 
> >>> container. The basic app structure was you would have your model's, 
> view's 
> >>> and controller's, and raft would load all these into the app, kinda so 
> you 
> >>> didn't have to code and express server or is server or what have you. 
> As i 
> >>> worked on raft and played around with it more i found that the MVC 
> style was 
> >>> much less dynamic then i would have liked. So from that the current 
> version 
> >>> has evolved. 
> >>> 
> >>> The current version... OK the current version is now very low leave, 
> in 
> >>> fact it does not do much other then load the app and its module in a 
> context 
> >>> with its own process. the only different between the raft context and 
> plain 
> >>> nodejs context is that you get a global called raft. what the raft 
> object 
> >>> does is gives you http, tcp, express server and so on. these servers 
> are 
> >>> just like the native server but for one difference and that been 
> >>> httpserver.listen, the native httpserver.listen take a port and host, 
> but 
> >>> what the raft httpserver.listen take is a string that is a domain that 
> gets 
> >>> routed to the port of that app. 
> >>> 
> >>> OK so like i say this is not an announcement but more a request for 
> >>> advice. 
> >>> 
> >>> Some of the questions: 
> >>> 
> >>> I know that nodester is hosted on AWS's and with that how many apps 
> are 
> >>> hosted per server? Are the server like a 8GB/RAM 4/core pc running 
> maybe 20 
> >>> apps per server, or is is a micro server running just one app? 
> >>> 
> >>> Nodejitsu are the developer of  haibu, but i dont think that is what 
> they 
> >>> are using for the PaaS. Now on that is their backend a custom build of 
> haibu 
> >>> or is it a whole new module in its own? 
> >>> 
> >>> To nodester. why did you chose git for the pushing of apps to the 
> backend? 
> >>> 
> >>> To nodester / nodejitsu. Have you guys thought of a kind of dynos 
> (heroku 
> >>> style)? if so how would you guys go about doing that? like you spawn 2 
> >>> processes of the same app and just route request to each app like node 
> does 
> >>> with the cluster module? 
> >>> 
> >>> To nodester. On average what are your costs running 3000+ app on 
> AWS's? 
> >>> 
> >>> OK so this is what im going to ask for now. I do have more question 
> but i 
> >>> would like to see if i get any answers for these ones. 
> >>> 
> >>> Gota love node! 
> >>> 
> >>> The code for now. Please note that this is not a release but a Q&A 
> >>> https://npmjs.org/package/raft 
> >>> https://github.com/FLYBYME/Raft 
> >>> 
> >>> 
> >>> Thanks all 
> >>> Tim 
> >> 
> >> -- 
> >> 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]<javascript:> 
> >> To unsubscribe from this group, send email to 
> >> [email protected] <javascript:> 
> >> For more options, visit this group at 
> >> http://groups.google.com/group/nodejs?hl=en?hl=en 
> > 
> > -- 
> > 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]<javascript:> 
> > To unsubscribe from this group, send email to 
> > [email protected] <javascript:> 
> > For more options, visit this group at 
> > http://groups.google.com/group/nodejs?hl=en?hl=en 
>
>
>
> -- 
> Joshua Holbrook 
> Head of Support 
> Nodejitsu Inc. 
> [email protected] <javascript:> 
>

-- 
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