在SQL/Oracle/其他后端中使用缓存(例如MS Velocity等) [英] Using caching (like MS Velocity etc) with SQL/Oracle/Other backends

问题描述

关于如何在我们的应用程序中使用缓存，使用SQL，Oracle和DB2作为后端，我一直争论不休.是的，由于遗留的数据库遍布各处，因此将它们全部一起使用.

现在，通过使用memcached编写一个小的概念验证应用程序，我已经看到了使用缓存的好处，但是我仍然需要说服自己更多.

我的主要问题是，由于像SQL Server/Oracle这样的RDBMS具有内置的机制来将最常访问的数据保留在内存中，为什么我们需要使用第三方缓存来复制这些数据?
我很想知道在应用程序(尤其是.Net)中使用第三方缓存的优点和缺点.
问候
Vijay

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

推荐答案

每个DBMS都有一种机制可以将常用的数据库页面和语句存储在内存中.但是它们不缓存结果，因此通常这就是为什么在客户端应用程序和RDBMS之间使用额外的缓存解决方案的关键所在.

例如，如果从DB加载了网页的内容，则不必每次都执行查询，并且将相同的结果返回给调用方.使用这种缓存解决方案可以减少DBMS的工作量，并(通常)减少网络中的通信量.

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.

这篇关于在SQL/Oracle/其他后端中使用缓存(例如MS Velocity等)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！