JAVA: when is it the best to use over other options server/site wise?

Please share your opinion -- when to use Java for a site's infrustructure?

[stlouislouis]

Hi,

I've been reading a lot lately on the various choices for a
website's backend/infrustructure. It seems to run the spectrum
from scripting languages like PHP and Perl running under Apache
to JSP/Servlets or EJB/J2EE setups.

My question is what are the appropriate places for Java in it's various
flavors (i.e. JSP, Servelets, EJB/J2EE, etc.)?

When would you, if ever, do a site's backend/infrustructure using
Java technologies rather than the scripting (or other) ones? Why?

Is there a dividing line of a site's size or amount of traffic?

Why do most large companies choose Java technologies rather than what
one more commonly reads about such as PHP, Perl or something similar?

Assuming you were adequately skilled in everything, is there one "better way" --
or can one say use tool "X" for sites like this, and tool "Y" for sites like that?

What are the guidelines? What makes sense? What's the rationale?

What has your experience been?

Thanks for sharing on this,

Louis

[txbakers]

IMHO, it all depends what you are comfortable with. If you know Java, then it is always the appropriate time and place to use Java. If you know VB, you would probably be better off sticking with ASP.

If you know Perl and C, maybe PhP is right for you.

There is no real hard and fast rule about what to use where anymore. With SunOne (Chilisoft) and Stryon's iASP, you can run ASP on Unix machines.

With JRun, Tomcat, and BEA you can run JSP and Java on a Windows box.

I don't think there is a "right" answer to this. Write in whatever suits your purpose.