Re: Terracotta and EOF
Re: Terracotta and EOF
- Subject: Re: Terracotta and EOF
- From: Andrus Adamchik <email@hidden>
- Date: Thu, 3 Apr 2008 21:28:54 +0300
I was toying with idea to use Terracotta as a possible clustering
solution for Cayenne ORM. Thought it can be used selectively for the
"cache" parts of the stack. But there are better, more targeted ways
to do cache syncing. The other thing - reattaching to the cluster
would only require terracotta if there is an uncommitted state in the
context, so that's more of a session persistence task (WO, not EOF).
So while the technology looks nice, I still don't see enough
motivation to try it for real with an ORM.
Andrus
On Apr 3, 2008, at 9:14 PM, Travis Britt wrote:
On Apr 3, 2008, at 1:00 PM, Mike Schrag wrote:
The issue is that EOF's problem is not that it's CPU or memory
bound, its problem is that it is a single-lock basically non-
concurrent architecture.
Yes, now that Wonder has better stack synching between and within
instances this might only be interesting if your stack has enormous
memory requirements.
Using it for the appserver layer is potentially interestesting, but
it's hard to get classloader separation within WO to be able to set
it up properly.
Hmm. Ideally this could (among other things) enable persistent
sessions, in that you might have an app instance (or collection of
instances) running over a cluster whose members can join or leave
the cluster without disruption.
tb
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden