If the answer is efficiency then I would respond "prove it", i.e. produce a test harness that produces the expected load so you can measure performance. Other factors you might consider (when choosing between any different technology):
- maturity: how mature is each technology? - adoptability: how accessible is the technology, how effective are the training vehicles (books, courses, public forums/blogs etc.) - "nice": how much do you "jibe" with the technology - some love Java, some hate it - understanding the somewhat subjective measure of "intuitiveness" is important if it is going to be used on a day to day basis - lastability: it is going to become unsupported before the end-of-life of your project (including maintenance) in other words, you need to answer "what are the risks of using technology X". For me, I choose both :) - having an asynchronous message based architecture allows you to write services in Clojure that use all the Clojure goodness or in Scala which use distributed Actors etc. Sometimes thinking bigger makes things simpler - instead of insisting everything is a shipped in a single deployable/technology why not use the right tool for the right job. Sorry - getting off track there.... -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
