Hi Vidar, Am Freitag, den 04.04.2008, 11:25 +0200 schrieb Vidar Ramdal: > We're building a large-scale web CMS, so scalability will be > important. Does anyone have any thoughts on how to cluster Sling > instances?
While I am not a specialist in Clustering, here are my thoughts. The basis is that the repository is being clustered, then most of the hard work has been done. Thanks to the JCR observation functionality, each Sling instance is notified on any changes and generally it is of no importance whether these changes came from with the same instance or from another repository cluster node. There are some points, which require more attention, like clustered eventing and replication, where you have an author and a publishing system and the authored and finalized content is pushed to the publishing systems. For the first situation, Sling already contains the event bundle, which implements this inter-cluster event handling using the repository for persistence and synchronization. The second situation will have to be handled on the level of replication, but here again, you might make use of clustered eventing to ensure exactly one single cluster node actually updates the content. Hope this helps a bit. Regards Felix
