On Thu, 7 Dec 2000, Scot Bellamy wrote:
> 1. If used extensively in a large scale system, this can lead to a very
> inefficient object design (too fine-grained). This will almost always
> result in a system that performs poorly and does not scale well.
However, if you're aware of this (and now we are :), you can
design with care to avoid it.
> 2. The EJB 2.0 specification will address much of the 1:1 mapping issue.
> I think, however, that another issue will become prevailent. That issue
> being that CMP ties the hands of the developer in tuning the SQL
> statements that access the database. As a result, it will be difficult to
> tune an application to perform as required.
I think I'd definitely try CMP first, where appropriate. Then if
you have performance issues with specific beans you could investigate
reimplementing them as BMP with optimized SQL, etc. But why spend all
that time up front, even for the beans that may perform OK with CMP?
Aaron
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
