The theory is that the more distributable the application the more scalable. Simply
add more machines to target the loaded parts of the app. Having fine grained EJB's
does mean your app is more distributable, however available network bandwidth would
come into play if the network overhead for all the remote calls gets high enough.
Another problem would be if a group of fine grained EJBs are fairly tightly coupled
and tend to need more resources all at the same time. In that case you're probable
not benefitting so much from having them split apart and may be better off having them
as a single bean.
Everything I've seen about it seems to suggest that it's a balance and about the only
absolutes are don't use 1 bean per table and don't use a single bean for your whole
app ;-)
-- Marc
> -----Original Message-----
> From: Peter Delahunty
> [mailto:[EMAIL PROTECTED]]
> Sent: November 21, 2000 11:09 AM
> To: [EMAIL PROTECTED]
> Subject: Answer me this, scalability !
>
>
> Ok I just want some outside opinions on this one.
>
> Does having more EJB's (ie, a fine grain design) make your
> application less
> scaleable. More EJB's means more remote method invocations and so more
> overhead, so does this impact scalability.
>
> comments ....
>
> ==============================================================
> =============
> 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".
