Hi, thanks for the suggestion, I just cross-posted this to the Scala group, adding a point that could help you help me (damn, my english..) with this choice. Here's the extracted part:
Please notice that the API should also have independent functionalities, > summoned by the apps, like file management (I want this document from this > app, the api knows how/where to fetch it), email sending and FTP handling. > Also, timed/recurring functions, like synchronizations between the apps' > databases. On Wednesday, February 27, 2013 8:30:02 AM UTC+1, Denis Bardadym wrote: > > Hi. > > If you want honest comparison write the same in Scala mailing list ( > scala...@googlegroups.com <javascript:>) (i did not see your msg in scala > group). > Other guys said alsmost nothing about choise you have on JVM. If you want > really async you can use Netty or Apache MINA (it is low level framewors). > But you should understand that if you want really write code in scala it is > other way to think then javascript. Fully rest frameworks for Scala you can > see is: unfiltered, spray, play-mini (uses play behind and uniltered > pattern combinators). > > BR, Denis. > > среда, 27 февраля 2013 г., 1:28:01 UTC+4 пользователь andreacode написал: >> >> 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
