[opencms] RE: [opencms-dev] more barriers to running in a cluster

[Jorge González]

In this scenario, the cms is modified on any node of the cluster.


One can think about other scenarios where the clustering helps to scale the
system up when the number of concurrent users "reading" contents raise. This
clustering scenario is simpler and could be implemented with db replication,
directory replication and one master cms server.

To change the contents, one must login on the master server. To read the
contents, the rest of the servers will do the work. So this reduces the
problem to manage the concurrent user publishing operations. If this number
is very high, in a user directed document repository for example, the
problem persists. Also master server is a single point of failure :(


	www.		Round Robin ---------  	cms1 	(shared session)
						---	...	(shared
session)
						---	cmsN	(shared
session)

	master.	---------------------	mastercms	-- synchronize (db,
webapp) on publish
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2076 bytes
Desc: not available
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20050906/fc49d517/attachment.bin>