On Fri, Jun 22, 2012 at 9:32 PM, Radhames Brito <[email protected]> wrote: > I have a medium size application in Rails that is consuming lot of > resources because it has to communicate with a SOAP web service, every > time the application accesses the service is the processing of the > request stops so i have to have start many instances to make the app > respond quickly to the other clients, i also have to start faye and > several background workers. > > So is it a better idea to port this application to node.js (expressjs) > and make async calls to the SOAP web service and update the clients > via socket.io?
That's exactly the use case node.js was designed for: shoveling loads of data from one network endpoint to another. > What kind of issues should i be aware of? That event-driven I/O is something of a paradigm shift. It takes some getting used to but if you've used e.g. EventMachine before, you'll be fine. -- 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
