Hi! This is Al from StrongLoop. Your project's objectives and use cases sound very, very familiar. We're already working with several other companies to build a similar piece of middleware that does API routing with little logic. I had this same problem back at my previous company where we did it in Java. Hindsight being 20/20, Node is much better suited for this without the added intricacies of needing to understand Java concurrency and the multithreading. As a company standing behind Node, we'd be interested working with you to help your business counterparts understand why Node is perfect for your use cases. Feel free to drop me a line - www.strongloop.com. Thanks!
Al StrongLoop <http://www.strongloop.com/> On Tuesday, February 26, 2013 1:28:01 PM UTC-8, andreacode wrote: > > Hi everybody! > > I need some help on getting together as much information as possible on > node.js (and its competitors), as we're going to start a quite project in > our company, and we currently are in that phase in which you have to > convince yourself and everybody else that this or that technology choice is > the right one. > > The project is about a "Proxy API", as I often call it, a *central > routing app* that should handle all the connections between our already > existing applications. These are like 7 at the moment, but we want to > separate some of them (especially the main one, a huge Ruby on Rails app > that computes and displays quite everything behind it), so we want to > create something very configurable, abstract, and prepared for future > expansion of new apps. > > Obviously, the main point here is *availability*, as everything in the > company (and perhaps, one day, our external clients as well) will > constantly hit this API, and ask (and post) data, but almost nothing as to > be computed in the API itself, we just pass the data to other apps, and > maybe do some nice *caching* to not constantly hit other apps always for > the same data. > > That said, we have to *convince the business counterpart* (we are a > financial company) that node.js is well-suited for our use case, is ready > for big numbers, and that (don't ask me why everyone in this damn sector > thinks this) Java, or better the JVM, may not be the best way to go. > Anyway, a nice comparison between the proposed languages would be very > appreciated! > > Thank you in advance in any case! > -- -- 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.
