Hi. I know nodejitsu. ;) > Nodejitsu are the developer of haibu, but i dont think that is what they are > using for the PaaS.
Actually, haibu is what runs everyone's apps on nodejitsu! We have a few closed source extensions for haibu, but aside from that it's all the same. In fact, I encourage you to use haibu as a starting point for something like raft. > Have you guys thought of a kind of dynos (heroku style)? We have a similar concept, called a drone (https://github.com/nodejitsu/haibu-carapace). Each haibu server (https://github.com/nodejitsu/haibu) can spawn n drones running whatever (multiple apps, or multiple copies of the same app). Our balancers can then proxy to these drones however we please. > On average what are your costs running 3000+ app on AWS's? My advice to you here would be to do this: 1) Figure out how many apps you can comfortably run on some AWS instance. Keep in mind that this is app-dependent. My parents' small business website doesn't need a whole lot of resources and could share space with a bunch of similarly quiet apps, but something like http://now.jit.su can (is) spread out over multiple machines of roughly the same size. 2) Figure out how much this chosen AWS instance costs. Baby ones cost less but give you less ponies. 3) ((cost/instance) / (apps/instance)) (number of apps) = (total cost). The math here is pretty simple; the tough part is estimating apps/instance. I can tell you right now that it's non-trivial. I doubt a single person could realistically afford to run 3000+ apps out-of-pocket, at least without seriously gimping each app's resources. > 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. Reminds me a little of geddy. The one thing I'll say, and many would disagree with me here (which is fine), but imo you should always be able to start a single instance of an app without clustering by running, say, `node app.js`. That said, there's certainly room for, `require('thing')({ models: modelsPath, views: viewsPath, controllers: ctrlsPath });` or similar if that's how you like to roll. :) I'd probably combine an approach like this with haibu were I trying to DIY a platform. > why did you chose git for the pushing of apps to the backend? In my experience: Developers are comfortable with git. Heroku uses git for deployment iirc, and no.de also used git for deployment. Nodejitsu uses jitsu+http because it allows us to use npm for app bundling. Hope this helps, --Josh On Sat, Aug 11, 2012 at 2:33 PM, Tim Dickinson <[email protected]> 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] > 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 -- Joshua Holbrook Head of Support Nodejitsu Inc. [email protected] -- 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
