Using caching (like MS Velocity etc) with SQL/Oracle/Other backends

Question

4.00/5 (1 vote)

See more:

Hi,

I am having big argument going on within my own head about using caching in our application which uses SQL, Oracle and DB2 as back-ends. Yes it uses all of them together because of legacy databases scattered all over.

Now I have seen the benefits of using caching by writing a small proof-of-concept application using memcached, but still I need to convince myself a little bit more.

My main question is that since the RDBMS's like SQL Server / Oracle have built in mechanisms to keep most frequently accessed data in memory, why do we need to duplicate that using third party caches?

I would love to know all pros and cons of using third party caching in applications (especially .Net).
Regards
Vijay

Posted 22-Mar-11 23:49pm

Vijay Gill

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Accepted Answer · 2011-03-22T23:54:00

Every DBMS has a mechanism to store frequently used database pages and statements in-memory. But they do not cache results so this is usually the point why use an extra cache solution between the client application and the RDBMS.

For example if contents of a web page is loaded from the DB, the query doesn't have to be executed every time and the same result returned to the caller. Using such cacheing solution reduces the DBMS workload and (usually) the amount of traffic in the network.