Clever Geek Handbook

Would you recommend Java / Glassfish / Metro for a brand new project?

I've developed in ASP.NET 2.0 for some time and a little less time in Java / Spring / Hibernate. I am now starting to develop a new web service and am confused with the choice:

.NET WCF 3.5 versus Java / Metro.

On the one hand, WCF looks like a brilliantly designed solution, a masterpiece of a programming framework, with all the support for functional languages, simple wizards, simple architecture. The downside is that it only runs on Windows (Mono doesn't support WCF) and doesn't integrate as nicely with Ruby on Rails (via JRuby as Java does).

And Java seems really outdated - no operator overloading or shared arrays ?!

So my main question is, can anyone start a new project using Java or is it just a dying language for legacy software?

PS. Both performance and database connectivity are top priorities, so this leaves slow Perl, Ruby or Python and unfriendly C ++ with data.

PPS. For the presentation layer, I am using Ruby on Rails.

-1


source to share


4 answers


If you're building a Rails app, JRuby on Glassfish is a winning combination. I have five Rails applications deployed to Glassfish and have not had any problems so far. I was impressed that performance and deployment were very easy.



+2


source


There is a lot of activity in the Java world. I speak with many clients about deploying new Java projects. I also see a lot of activity in JRuby and other dynamic languages. Take a look at the Tiobe index for more: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html

As far as Metro, on GlassFish you can call Java libraries from dynamic languages ​​(and vice versa), so Project Metro with Java, JRuby, etc. is an option.



John Klingan, GlassFish Group Product Manager

+1


source


Your observation is pretty bold, I think. the main thing is necessary. you need shared arrays for everything, or you can handle all things efficiently without the help of shared arrays ... :) and Java is not obsolete .. it is actually GIANT. v. big GIANT. it depends on your project, how you are going to control it, and what services you are going to launch, as you yourself talked about SD. take a snapshot in Java, you surely live in it :)

0


source


I would assume that both suggestions suit your needs equally well. So when you are more familiar with .NET tools and libraries, you should stick with it as there is no value in learning two things that do (roughly) the same thing. Especially when these things are difficult.

0


source






More articles:


All Articles