Thank you Guillermo. So I'll end up with 3 (probably more in the future) apps that talk to each other using socket.io. is there a good way to manage them and not getting lost with the configuration and provisioning?
I noticed a few project by substack that might be relevant, but I don't understand them ): https://github.com/substack/fleet https://github.com/substack/airport https://github.com/substack/zygote https://github.com/substack/seaport Another question - I looked at dnode (https://github.com/substack/ dnode). you can make remote calls from the browser to your server using it. What is the main difference between dnode and socket.io? On Apr 22, 12:02 pm, Guillermo Rauch <[email protected]> wrote: > Separating responsibilities between different apps is almost always a good > choice. Communicating those apps through messages (eg: ømq) leads to good > architecture. > > -- > Guillermo Rauch > LearnBoost CTOhttp://devthought.com -- 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
