I'm considering building clustering on top of Castor. Any advice? Previous messages in this thread suggested some ideas. Have they been deployed? In a large high-volume production cluster? Successfully?
It worries me that the released Castor code doesn't support cache invalidation. I'm selecting software for a web-based application with a fairly large and complex database. There will be many concurrent users, and clustering will be required. There is a fairly large set of data that most users need to see frequently, but is modified infrequently. Users can tolerate seeing stale data, within a staleness time limit of several minutes. Optimistic concurrency control is adequate. Users can tolerate denial of an update request when they lose a 'race' with another user modifying the same database row. Such an application will be most scalable, I estimate, if each application server maintains a cache that is shared by concurrent users. For best performance, the servers should cooperate to keep their caches loosely coherent. That is, after modifying data they should eventually notify each other to refresh cached copies of the modified data. I'm prepared to make the servers notify each other. But the server that receives such a notification needs a mechanism to invalidate (or refresh) stale cache entries, including Castor's cache entries (if Castor is used). - John Kristian P.S. Previous messages in this thread were: From: Adamo, Vince Date: Mon, 15 Jul 2002 08:06:05 -0700 http://www.mail-archive.com/[EMAIL PROTECTED]/msg08406.html From: Tim Fox Date: Thu, 16 Aug 2001 01:37:32 -0700 http://www.mail-archive.com/[EMAIL PROTECTED]/msg00609.html ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
