Page 2 of 2
Re: Large scale website - which concept/design to use?
Posted: Thu Apr 23, 2009 4:04 am
by wei
The question was not whether memcache scales or how fast memcache is, the question was regarding where session data should be stored. My view is that memcache may not be suitable for this task.
Re: Large scale website - which concept/design to use?
Posted: Thu Apr 23, 2009 4:18 am
by Benjamin
wei wrote:The question was not whether memcache scales or how fast memcache is, the question was regarding where session data should be stored. My view is that memcache may not be suitable for this task.
I have to disagree. I believe memcache is perfectly suitable for storing session data.
Re: Large scale website - which concept/design to use?
Posted: Thu Apr 23, 2009 6:44 am
by kaisellgren
A session is more or less a cache.
Re: Large scale website - which concept/design to use?
Posted: Thu Apr 23, 2009 9:55 pm
by wei
If the session data may be permitted to be lost, cache may be used, but this is not always the case and usually not the desired behaviour.
Re: Large scale website - which concept/design to use?
Posted: Thu Apr 23, 2009 10:02 pm
by Christopher
When you say "lost" you mean either by a system failure or by a developer set expiration time. The exceeding rare and very controllable. If you want session data to be essentially permanent then DB would be the way to go.
Re: Large scale website - which concept/design to use?
Posted: Fri Apr 24, 2009 12:34 am
by wei
can also be lost when cache becomes full
Re: Large scale website - which concept/design to use?
Posted: Fri Apr 24, 2009 1:09 am
by kaisellgren
Huh? Storing sessions in the database means that they stay there until the database has corrupted by either a hardware failure or a software failure unless, of course, someone removed them. I consider this as a "permanent" data storage. If you want a more "permanent" storage option, you are out of luck. Even if you write session data onto a paper with your pen, the text will eventually disappear..
Re: Large scale website - which concept/design to use?
Posted: Fri Apr 24, 2009 1:54 am
by Benjamin
I don't know, maybe we are talking about two different things here. Sessions can be considered a cache, sure why not. The notion that they need to be persistent and/or redundant is a bit off though....
Re: Large scale website - which concept/design to use?
Posted: Fri Apr 24, 2009 3:31 pm
by John Cartwright
astions wrote: The notion that they need to be persistent and/or redundant is a bit off though....
I agree. Sessions should only hold information related to it's particular
session (i.e. not permanent). Maybe the OP needs to explain this philiosophy more.
Re: Large scale website - which concept/design to use?
Posted: Sat Apr 25, 2009 2:13 am
by kaisellgren
John Cartwright wrote:Sessions should only hold information related to it's particular session (i.e. not permanent).
+1
Re: Large scale website - which concept/design to use?
Posted: Tue Apr 28, 2009 8:00 pm
by josh
Store them on disk and partition your userbase