memcached "backends"
Ask Bjørn Hansen
ask at develooper.com
Thu Oct 12 22:54:26 UTC 2006
On Oct 12, 2006, at 15:06, Andy wrote:
> Maybe part of the problem is the way memcached is commonly
> described, as
> Andy did above, with the words "a caching layer between my application
> and database". The key word being "between". It logically sits
> between
> them, but physically, memcached is more of a peer of your reliable
> backing store, rather than a link between the frontend and the
> backend.
> Your "frontend" goes to one source, if it's not there, it goes to the
> other.
Depends on your perspective; in some cases then the memcached use is
implemented in the "model layer" ("in between") so your "front end
code" (controllers / views) just magically gets the cached data when
available and appropriate.
- ask (who doesn't have a need or particular interest for other
backends either - although the NDB backend could be neat and possibly
useful)
--
http://www.askbjoernhansen.com/
More information about the memcached
mailing list