RE: Application Server Caching

[Nelson, Allan]

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.  The businesses that this is true of are small in number.   Allan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Sent: Wednesday, January 14, 2004 4:14 PM To: Multiple recipients of list ORACLE-L Subject: Application Server Caching I heard a presentation from a front end performance analyst last night from www.tangasol.com (im not associated with them at all). He was pretty impressive.   He argued that accessing the database is expensive. He also argued in favor of caching data at the application server level. Have any of you worked with this? What are your opinions? His opinion was that people go back to the database to ask the same question way too often and cause a botteneck, if you can cache these frequently asked questions at the front end, it will significantly scale better. ______________________________________________________________________________ This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Copying, forwarding or distributing this message by persons or entities other than the addressee is prohibited. If you have received this email in error, please contact the sender immediately and delete the material from any computer. This email may have been monitored for policy compliance. [021216]