Hi

I don't have a link to provide you. I heard this information from the
software architecture team of the company I am working with. They had a
meeting with consultants from Sun microsystems. It seems they had cautioned
against use of entity beans in high-volume production sites. The reason put
forth was that the current crop of app. servers show a degraded performance
when there are a large number of entity beans.

I am trying to get more information on this so that I could discuss it in
the mailing list.
Regards
Anup



                    James Cook
                    <[EMAIL PROTECTED]        To:     [EMAIL PROTECTED]
                    M>                       cc:
                    Sent by: A               Subject:     Re: Entity beans vs DAO(Data 
Access
                    mailing list for         Objects)
                    Enterprise
                    JavaBeans
                    development
                    <EJB-INTEREST@JAV
                    A.SUN.COM>


                    03/26/2001 11:47
                    AM
                    Please respond to
                    A mailing list
                    for Enterprise
                    JavaBeans
                    development






----- Original Message -----
From: "Anup Maliyackel" <[EMAIL PROTECTED]>

> 1)Everybody (including sun) agrees to some extent that entity beans are
> performance bottlenecks and they don't scale well. Can somebody elaborate
> on this?

You will have to send me a link on this one. I have a hard time believing
that
Sun considers entity beans to be performance bottlenecks. Inless of course,
they
imply that persisting data is a performance bottleneck. If that's the case,
I
agree. ;-)

> 2)How do different implementations of Entity beans differ in terms of
> clustering in different app. servers?

Entity bean design does not differ in a clustered environment. There was a
time
when WebLogic was advocating a pessimistic locking scheme in their
standalone
containers. When developers leveraged this in their design, they discovered
problems when moving to a clustered environment. Lesson learned, the
database is
the only true locking mechanism.

> 3)If entity beans are not the way to go,what next? ; Session Beans+DAO;
JDO
> etc?

Give me a reason why I would want to use JDO instead of CMP Entity Beans.
DAO
means nothing. It's just an implementation pattern. For example, I use DAO
when
writing BMP Entity Beans.

> 4) what is the status of JDO specs? Can we expect something anytime soon?

Not much news yet...

http://java.sun.com/aboutJava/communityprocess/jsr/jsr_012_dataobj.html

jim

===========================================================================
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".

Reply via email to