Hi, I know Nodester, which we are running at Cloudnode:
> 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? You probably need to be flexible here. Nodester, unlike us, is running on one big instance, which means there is a limit of how much apps can run. Others doing the micro server per app thing are also getting into trouble. They need 3000+ IP addresses which are a limited resource and you have to explain your demand to RIPE. You need very good monitoring and balancing to dynamically find an optimum in between these models. > To nodester. why did you chose git for the pushing of apps to the backend? Git can do multiple protocols and can go thru client side firewalls. As it is a VCS you never loose track of you apps and see what has changed when. We have also installed Gitweb to allow users direct access to their repositories compare versions and re-download what they need. (http://gitweb.cloudno.de) Also as Josh said, devs are comfortable with it. - Hans On Saturday, August 11, 2012 11:33:21 PM UTC+2, 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] 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
