Ian McCallion writes:
> The whole idea of optimisation by caching in the JVM to avoid DB access and
> (re)construction of objects from data is somewhat suspect. It can and will
> be done but it only works in special cases where there is a clean
> relationship between database rows and EBs and is fundamentally
> non-scaleable to multiple JVMs and clusered systems.
On this last point, the folks at Persistence and here at GemStone might
differ with you a bit.
GemStone/J's caching capability is based on an integrated persistent object
store, accessible concurrently - and transactionally - from a large number
of independent Java VMs on one or more distinct machines, via shared
memory. Yes, the relationship between object models and the relational data
they represent can be tricky to establish and synchronize, but once cached,
our system does allow scaleable access to the cache from multiple JVMs and
clustered systems.
Marc San Soucie
GemStone Systems, Inc.
Beaverton, Oregon
[EMAIL PROTECTED]
===========================================================================
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".
