Search squid archive

Re: Squid vs caching products like memcached

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Words by lightbulb432 [Wed, May 16, 2007 at 08:16:44AM -0700]:
> 
> What’s the difference between the reverse proxying features of Squid and a
> caching product like memcached?
>

Memcache has nothing to do with proxying. Squid talks http and caches
http objects, memcache talks the memcache protocol and caches objects
(can be the key/value you want). memcache is not related (directily at
least) with http, it is just a cache engine, you have to program around
it to turn it into something useful.

> 
> I don’t necessarily mean specific comparisons of both products (e.g.
> performance), but rather explanations of what both types of products do. I
> understand that there are some large-scale websites out there that make use
> of both, so clearly they are better at different things and both have a
> place in a given architecture.
> 

Yes. At first Squid is something you put between the cliente and the web
server. Memcache is something you put between your web servers and your
database/filesystem/whatever, it stays on the backend.

-- 
Jose Celestino
----------------------------------------------------------------
http://www.msversus.org/     ; http://techp.org/petition/show/1
http://www.vinc17.org/noswpat.en.html
----------------------------------------------------------------
"And on the trillionth day, Man created Gods." -- Thomas D. Pate


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux