> > * What happened to the original dream that node would run in a network of
> > > nodes, which would together make up your app? > > > > Lots of people are doing this now. (Walmart, stackvm, Joyent, and the > > npm website all come to mind.) > > And how's the experience been so far? > In comparison to developing and running a single-process app, this quite > super difficult and the experience is bad. > You can add Adobe to the list, and so far I've found that there are trade-offs, but it's similar to building any service-oriented architecture. You get the advantage of reducing complexity by breaking a problem into smaller parts, but the additional overhead of managing more separate projects. Deciding where to dice things up and how is the hardest part, probably, but those decisions tend to get easier as your projects progress. New services (nodes, if you prefer) tend to suggest themselves. Performance implications also come into play -- do your different components need to communicate in a manner that would be major bottlenecks over IPC or across network lines? Maybe those modules should run in the same process. I still think this is valuable advice: Don't build a large application. Build lots of small ones, instead. Node makes that pretty easy. -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
