> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 27, 2000 10:03 AM
>
> You said it yourself. Use EJB's when you need to and don't
> when you don't.
I think a big part of the problem is that EJB-based app servers
are being massively hyped and oversold by the vendors, simply
because they're profitable flagship apps. Many customers never
quite realize that they aren't using any functionality aside from
what's provided by the servlet engine. Many others misuse EJBs
and thereby fail to get any benefit from them that could not also
have been obtained from a simpler non-EJB app.
As has been said many times, but bears repeating: If you need
solid transaction management, high availability, and session-
aware clustering and load balancing with transparent failover, an
EJB app server is probably the right choice. If you don't, there
are far cheaper and simpler options.
Also, note that any nontechnical executive will claim that each
of these features are "necessary". A cost comparison can often
retune the necessity index.
It's all just another case of silver bullet syndrome. Whatever
the latest gold-plated software tech is, it's always going to cure
cancer and solve world hunger and regrow hair. People stampede
to adopt it, then turn on it savagely, and then finally a few years
later it's just another item in the tool box. I've watched it
happen several times during my career (AI, object orientation,
Java, and so on and on).
> There is nothing illogical about that nor is there anything in Turbine
> preventing you from doing that.
Shall I submit a J2EE-preventing patch? :)
--
Craig Berry - (310) 570-4140
VP Technology
GlueCode
1452 Second St
Santa Monica CA 90401
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
