title: RDBMS result caching vs Application level caching?
body: <p>In 10 years of mine experience, we used RDBMS either Oracle or SQL server with configuration by default. Never tuned the result cache which is disabled by default(at least in oracle).I have always seen using the cache options at application level like ehcache/memcache/redis etc as caching solution.</p>
  
  <p>Question - Is it not a great option to use the result cache i.e. DB level proactively whether or not I face any performance issue provided I have memory bandwidth available on DB server ?
  with this query results say <code>select * from employee where department = 'Finance'</code>  will always be cached corresponding to finance department. </p>
  
  <p>My question is why not use DB level caching if hardware can support it with LRU or appropriate algo per specific requirement instead
  of application level caching where I need to create keys, deploy it(like memcached) as separate server ?</p>