Ryan,
He has a point. If you look at 9IAS's architecture
there is a cache database at the apps server. The trick is to know when
the data your looking for in cache is no longer valid. A certain
children's apparel/toys site did that to me back in October. I'm still
torqued at them.
Ryan,
Our application does a certain amount of application server caching, and
infact has a pretty advanced cache mechanism to deal with out of date
objects, etc.
On a more simple level - Common reference records are loaded at start up
and cached, error messages are cached, etc. In a similar
an.com.au> cc:
Sent by: Subject: Re: Application Server
Caching
[EMA
Obviously. The issue has been whether or not Oracle's data caching
worked well - and was read for prime-time in earlier versions.
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of RyanSent:
Wednesday, January 14, 2004 5:14 PMTo: Multiple recipi
Title: Message
He's
right, accessing the database is expensive. So is accessing from an app
server if you have to support concurrency, updataing, transaction
control, etc. Only if you consider the ACID properties of databases
of no use for your application is this line of argument correct.
SAP R/3 has taken advantage of this approach for a long time now. It buffers
tables based on settings in the R/3 data dictionary and can buffer single rows,
groups of rows, or entire tables. Tables which are used to store configuration
information are typically fully buffered, while transactional
