there should not be any downtime due to heavy load and hits
Or rather "Java EE" now, since Sun wanted to drop the abbreviation to "J" as well as the unnecessary 2...
I hope you mean JEE now?
As you say, everything is about trade-offs. In general I agree that Java, PHP, ASP etc. are all going to be fine for programming websites. I use Java EE for the "more-than-average" Web site because the plethora of Java APIs makes it a breeze to do difficult things. On the desktop the benefits of platform independent bytecode make Java easy to deploy, especially via the Web as applets or through JNLP.
A JVM is horribly hungry, weighing in at over 100MB of RAM on most platforms. But when you put in charge of a complex workload, the overhead gets diluted to the point where the advantages offered outweigh the disadvantages.... I likewise pretty much gave up on C when Java began meeting or exceeding it on performance tests...
Originally posted by Charles Lyons:
I also recall a thread on this forum about FFT routines and someone commented that the routine in C++ was comparable to Java. IIRC, in C it was 2 times faster, and in assembly was 8 times faster. In DSP, those speeds matter, so using the assembly version is ideal.
Originally posted by Tim Holloway:
Most business apps, online or not, are data-intensive, not compute-intensive.