Ben,
For what it's worth, we have many customers building
EJB applications for the Internet. Sure you could
do the same with CORBA, but You have to build
the server framework infrastructure. With EJB this
is prescribed.
On performance, you can arcitect EJB's for performance,
you just have to be careful with component granularity,
and not instantiating zillions of entity beans in the context
of finders. You also have to be concious of what is
flowing over the wire. You have to do this with CORBA
too.
On session beans vs. regular old Java objects, session beans
gain the the ability to implicitly participate in transactions as
needed. You'd have to hand code this outside the EJB model.
This is perhaps not a big win in the context of a simple query,
but it is a big win when you components start to Do something
(business logic).
At the end of the day, and application that does nothing but
pull from db's to build html pages may not benefit much from EJB.
Apps with more business logic begin to benefit, and as you move
toward reusable components is the big win.
-Chris.
----------------------------------------------------------------------
Chris Raber, Systems Engineer, GemStone Systems Inc.
100 West Big Beaver, Suite 200, Troy, MI 48084
phone: (248)-680-6691, fax: (248)-680-6689,
email: [EMAIL PROTECTED]
web: http://www.gemstone.com/
----------------------------------------------------------------------
> -----Original Message-----
> From: Ben Engber [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, May 13, 1999 1:36 PM
> To: [EMAIL PROTECTED]
> Subject: EJBs and the internet
>
> Does anybody have an idea whether it's appropriate to try and use EJBs in
> an Internet application?
>
> From people I've talked to, most high traffic sites have given up CORBA
> based appservers for direct database access because they just didn't
> perform at traffic levels of more than a few hundred thousand page views
> per day. I've been building a large application based on EJB, and am
> concerned about performance.
>
> I guess my question is what do EJB's buy me? It seems that they offer a
> simplified programmatic interface for transactions, but at the expense of
> performance. If that's the case, then I'd rather stay away from them.
>
> On the other hand, it seems like Entity Beans could handle in-memory
> caching of data, greatly reducing SELECTs on the DB. But my
> implementation
> (WebLogic) doesn't do this implicitly, which makes me wonder again, what
> are they for?
>
> Similarly, I've been reading with interest the recent discussion about
> moving entity bean finder methods over to session beans. It makes a lot
> of
> sense to me. Can someone tell me the advantage of having these methods in
> a session bean rather than in a regular Java class?
>
> -Ben
>
>
> --
> Ben Engber
> Software Engineer
> The New York Times
> [EMAIL PROTECTED]
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
