Thanks for your suggestion! Unfortunately, I see no big involvement in the vert.x community (I've to say that the github repo for vert.x modules<https://github.com/vert-x/vertx-mods/tree/gh-pages/mods> is a bit desolating), and if possible is even younger and not enterprise-ready than node. IMHO, of course.
On the other hand, I find that presentation really interesting, also because is really fresh (from just some weeks ago) and those "Aggregation and Spindrift" points are quite enthralling. Thank you so much! On Wednesday, February 27, 2013 5:39:19 AM UTC+1, andy wrote: > > Not much help here, but maybe vert.x is a good compromise (JVM based, but > you can use an async approach and write JS code): http://vertx.io > > The other thing that comes to mind is something I saw Mike Brevoort > present on. See > https://speakerdeck.com/mbrevoort/node-dot-js-and-me-denverjs-january-2013, > specifically the slides on Aggregation and Spindrift. > > andy > > On Tue, Feb 26, 2013 at 2:28 PM, andreacode <[email protected]> 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. >> >> >> > > -- -- 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.
