That
is fuzzy logic of the week-end ;)
For
entity beans, we let the database synchronize the beans (through select ... for
update) consequently, we do not need/have a distributed cache at the application
server level. Consequently, your calls can either be redirected to S1 or S2: the
bean will be fetch from the database (because it needs to lock it anyway.) See
the ML about previous discussion about optimist/pessimist locking at the
database/AS level: some parts are interesting for clustering too. Some more
features could be added in the future for read-only beans.
Remember that clustering means higher availability and in some cases
better scalability but it also has a cost! Even with a distributed cache, this
would have a cost.
Cheers,
Sacha
|
- [JBoss-dev] Clustering is available for use Bill Burke
- RE: [JBoss-dev] Clustering is available for use marc fleury
- Re: [JBoss-dev] Clustering is available for use Rick Gibbs
- RE: [JBoss-dev] Clustering is available for use marc fleury
- RE: [JBoss-dev] Clustering is available for use Sacha Labourey
- Re: [JBoss-dev] Clustering is available for us... Rick Gibbs
- RE: [JBoss-dev] Clustering is available fo... Sacha Labourey
- RE: [JBoss-dev] Clustering is availab... Bill Burke
- RE: [JBoss-dev] Clustering is ava... Sacha Labourey