|
|
Posted by David Haynes on 01/07/06 05:06
Balazs Wellisch wrote:
>> The loadbalancingpart is however irrelevant if you use a database for
>> sessionstorage, since every session will contact the same database that
>> stores the sessions.
>> (If you plan to use more databases for sessionstorage, I give up. :P)
>
> Yeah, the obvious solution is to store all the session information in a
> single database. But that would limit the failover capability of the system.
> I was thinking about setting up each box with its own copy of the database
> and replicate the data between each one. However, I don't think this is a
> feasible solution since session info changes all the time and I can't have
> the dbs continuously replicate themselves all the time. I suppose I could
> use sticky sessions, but I was wondering if there was a better solution out
> there.
There are a number of database technologies that will allow you to set
up replication even in high transaction environments. Oracle's RAS for
example.
Another option is to model the sessions through a persistence object
that uses a database as a backing model. . (Think queries answered from
the persistence object, writes go all the way through to the database,
missing queries are answered from database)
-david-
Navigation:
[Reply to this message]
|