One possible scenario that an EJB container with a good CMP engine would
support (vendor plugs come here):
The EJB server will load balance the client requests to any number of
servers in a cluster, each one will load it's own copy of the entity
bean, without the overhead of sharing but with the overhead of more
database hits. At some point caching kicks in and improves performance.
If your entities are read only and are not modified, the CMP engine
should not attempt to store them. But having the same entity on any
number of machine gives you the form of replication and clustering you
need. If conflicts do occur when storing, the CMP engine should be able
to detect that through dirty caching.
arkin
> The problem is scaling and capacity based designs to handle 100k's
> concurrent customers doing Use cases that require short latencies to
> every few second BOM events. Many of our Entities are read 99.99% of
> the time, so why make them shared Entities, but we need replicated,
> clustered Entities for scaling and capacity. TOPlink claims to
> solve this problem ???
>
> Any experiences? I.E. with weblogic 5.x and replicated exclusive
> Entities?
>
> Thanks,
>
> curt
>
> Curt Smith
> Z-Tel
> email: [EMAIL PROTECTED]
> work: 404-237-1166 x182
> FAX: 404-237-1167
>
> ===========================================================================
> 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".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
