I am trying to determine how well the existing EJB spec
and the forthcoming JDO address the issues of read-only
or read-mostly non-transactional applications where
fail-over and load-balancing are needed. If I need to
access a persistent Java component model where the
underlying data (say a catalog of parts) changes
infrequently. And the application requires low response time
(suggesting need for an in-memory cache). And I'd like to
transparently deal with machine fail-over and load-balancing
(suggests an app server).
Is a stateless session bean in front of a home-grown cache
the obvious way? Will JDO implementations give me fail-over
and caching?
Any comments?
Peter Booth
===========================================================================
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".
