Business logic layer - what to use?

[Matthew Carpenter]

Shawn L Johnston wrote:

>
> It seems to me that there is a huge difference in JVM's as well as OS 
> for Java. Stupid example but running JBoss on a OpenLinux eDesktop 
> P233 with 128 mb of ram took 2-3 minutes to start up with Sun's 1.3 
> JRE. With IBM 1.3 JRE it took around 30 seconds (about 2 years ago).

The IBM for Windows JVM was the best of the best back then.  Sun's 1.4 
and IBM's 1.4 became pretty equivalent.
Check out volano.com for their VolanoMark performance measurements.

>
>>
>>
>> Another thing about Java is this : don't believe the hype! There are 
>> some myths about Java that just give it a bad name. For example, some 
>> people say that memory management is better in Java because you don't 
>> need to understand and use pointers. Well, that gives a lot of people 
>> the wrong impression that memory management is better. If you create 
>> a lot of objects and don't bother to dispose of them (no, you cannot 
>> trust the garbage collector), you will encounter memory problems 
>> worse than Visual Basic -- in fact, your program may not even run.
>>
> Well said!

I disagree.  I agree that you must check out Java and make up your own 
mind.  I agree that hype (pro and can) have gotten out of hand.  But the 
memory management example doesn't compute.
First off, unless they've changed things recently, Garbage Collection is 
the only means of recapturing the memory.  
Secondly, GC depends heavily on the JVM.  eg.  IBM used to call the Sun 
GC code the "Stop the World" garbage collector.  I know that it was 
because while stress testing my app server code in 99 with the Sun JVM 
I'd watch memory shoot straight to the roof, then when it ran out, major 
performance hit while the GC cleaned up.  IBM implemented a more 
graduated GC which performed better overall...  
It's not about "disposing" of them, it's a simple " handler=null;"  The 
GC still does the rest.  But you are correct in  this:  If you don't 
code smart, you shouldn't code at all.  Pay attention to what your code 
is doing.  Plan it on paper first.  Make the "logical" overhead complete 
(or as close as possible) before powering up the editor/IDE.