Why reinvent the wheel? I'd say a session bean in front of
a commercial high performing persistent cache is the obvious
solution. We've used Gemstone/J very successfully in a project
with similar requirements. It provides the caching, load balancing
and fail over out of the box. http://www.gemstone.com
Frank Sauer
The Technical Resource Connection
a wholly owned subsidiary of Perot Systems
Tampa, FL
http://www.trcinc.com
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Booth
> Sent: Sunday, June 25, 2000 4:57 PM
> To: [EMAIL PROTECTED]
> Subject: JDO or EJB for read-mostly components?
>
>
> 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".
>
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
===========================================================================
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".
