Jon Dart wrote:
>
> ...
>
> However, this isn't a very common programming paradigm. Keep in mind that your
>database server is going to cache frequently read data anyway. If you have a nice
>fast database server and effective connection pooling (so you're not having the
>overhead of reconnecting), you may find that pulling this frequently-accessed data
>out of the DB is not a great deal less effective than pulling it out of your cache.
I doubt it. We have generally found that such caches give 30-40 times the
performance of hitting the DBMS, no matter how effective the DBMS cache is.
> Also you may have a problem with your architecture re updates. E.g. if some
> person or process ever updates your DB tables directly, you will have a stale
> cache in your server.
Check with your vendor for their support for dealing with this.
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
