On 2001.05.01, Tim Darling <[EMAIL PROTECTED]> wrote:
> Further Enterprise Java Beans make websites that are
> much faster because a DB call isn't made every time a user hits a
> page.  DB calls are 1,000 - 10,000 times slower than a call to a java bean
> which is acting as an abstraction of the database.

I can implement the equivalent of Java beans using two or three
procs that act as wrappers around an nsv_* interface, all in
Tcl and AOLserver API.

BMP (Bean-managed Persistence) is known to be pretty poor as far
as I've heard (this may be wrong, especially in the newer J2EE
stuff), and the overhead of having a few hundred thousand
instances of Entity beans is said not to scale really well without
extraordinary system resource requirements.

Overall, I liken EJB to the equivalent of Visual Basic -- perhaps
really quick to hack together really poor architecture given the
amount of abstraction away from the actual intimate lower-level
details, but that means you're relying on the implementation of
the abstraction layer to be done really well.  EJB isn't quite
there, yet.

- Dossy

--
Dossy Shiobara                       mail: [EMAIL PROTECTED]
Panoptic Computer Network             web: http://www.panoptic.com/

Reply via email to