Hello Al,
Al Fogleson wrote:
> Yes and no. There is a terribly large amount of overhead involved in
EJB to begin with
Which overhead are you referreing to by this? The overhead involved
should be low compared to the optimizations that are done to speed up
data access.
> then you start adding all the RMI calls over the network and that adds
some load too
Well, EJBs will not always be called remotely to start with. A very
common scenario is that you write Servlets/JSPs that communicate with
EJBs. Usually you will run your Web components and EJBs on the same
servr and no RMI calls will be made. Of course though, if you need the
remote access it will be used. But that is an overhead you need no
matter what technology. Orion's RMI-transport protocol is very
optimized.
>There are some situations, especially when doing the kinds of things
you are talking
>about where BMP is the only way to go. Because of complex joins or the
need for a
>complex primary key. it does put more work on the bean developer but in
some cases
>it may be the only way to go.
Yes, in a few very rare cases you need BMP because of the full control,
but whenever you do, stop and think about wether you really need it. In
most cases when BMP is used it's not really necesseary. And with BMP, as
always, you won't get the performance of CMP and it won't be as simple
to change database.
Regards,
Karl Avedal
