caching

TwitterFacebook
Get flash to fully experience Pearltrees

How Google Taught Me to Cache and Cash-In | High Scalability

A user named Apathy on how Reddit scales some of their features, shares some advice he learned while working at Google and other major companies. To be fair, I [Apathy] was working at Google at the time, and every job I held between 1995 and 2005 involved at least one of the largest websites on the planet. I didn't come up with any of these ideas, just watched other smart people I worked with who knew what they were doing and found (or wrote) tools that did the same things. But the theme is always the same: Cache everything you can and store the rest in some sort of database (not necessarily relational and not necessarily centralized). http://highscalability.com/how-google-taught-me-cache-and-cash
http://architects.dzone.com/articles/role-caching-large-scale

The Role of Caching in Large Scale Architecture | Architects Zo

We Recommend These Resources Pre-Internet, lots of systems were built without caches. The need to scale has led to the widespread deployment of caching.
A lot of us heard the word cache and when you ask them about caching they give you a perfect answer but they don’t know how it is built, or on which criteria I should favor this caching framework over that one and so on, in this article we are going to talk about Caching, Caching Algorithms and caching frameworks and which is better than the other. The Interview: "Caching is a temp location where I store data in (data that I need it frequently) as the original data is expensive to be fetched, so I can retrieve it faster. http://javalandscape.blogspot.com/2009/01/cachingcaching-algorithms-and-caching.html

Intro to Caching,Caching algorithms and caching frameworks part

What is Memcached? Free & open source, high-performance, distributed memory object caching system , generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load. Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

memcached: a distributed memory object caching system

http://www.danga.com/memcached/
http://commons.apache.org/proper/commons-jcs/index.html Java Caching System

JCS - Java Caching System

Too-biased - Tobias Luetke's thoughts

The Apprentice Programmer I dropped out of school when I was 16 years old. School was not for me. To me, computers were so much more interesting. Right or wrong, I felt like I wasted my time there and my real education was starting when I came home. http://blog.leetsoft.com/2007/5/22/the-secret-to-memcached
http://www.devx.com/dbzone/Article/29685

Speed Up Your Hibernate Applications with Second-Level Caching

igh-volume database traffic is a frequent cause of performance problems in Web applications. Hibernate is a high-performance, object/relational persistence and query service, but it won't solve all your performance issues without a little help. In many cases, second-level caching can be just what Hibernate needs to realize its full performance-handling potential. This article examines Hibernate's caching functionalities and shows how you can use them to significantly boost application performance. An Introduction to Caching Caching is widely used for optimizing database applications.

OSCache

http://wiki.opensymphony.com/display/CACHE/Home Unfortunately, OpenSymphony has seen it's final days. Started originally by some of the great minds of open source Java, it had a great run and produced some of the best open source Java libraries out there: WebWork (now Apache Struts) and XWork, it's core engine Quartz Scheduler SiteMesh Compass OSCache OSWorkflow OGNL OSUser PropertySet Clickstream OSCore Some of these projects have moved on: WebWork lives on in Struts and Quartz, SiteMesh, and Compass all have their own homes now. But others have been left stagnant for years and were unfairly misleading to developers, giving the impression that they were viable projects even though no one had been involved in years. Rather than continue to mislead developers about the state of the projects, we've decided to lay it all out there and hope that the interesting projects will eventually get forked and live again on another site such as Google Code , Github , or Bitbucket .