I'm looking for an evolutive architecture for my application.
this is a web site that is gonna grow up rapidly.
I'd like to know where and how I can store current user sessions.
The application is not clusterised yet.
but if it happend tomorrow, I don't want to redevlop my session gestion.
is TomcatClusteringCache performant to store and replicate sessions ??
Is that takes much resources ???
Should I prefere to store sessions in a particular database??
What king of load ballancer should I use???
have I to use the JBoss AS as load ballancer exclusively ???
Should I use an hardware load ballancer??
is there any problems with SessionID duplicate??
I know that on MS .NET the common architecture is to store session on a database to avoid load ballancing problems and cache replication.
From my experience session replication has indeed an impact on performance. If you use a sticky-session cluster (see below) you should evaluate if you really need session replication.
I do not think so. All common DBs perform quite well.
have to evaluate if this justifies to replicate every session.