Hi,
We have a client interested in using Alfresco for content management. The organisation is global and, therefore, offices are geographically distributed around the globe.
One concern the organisation has is the performance of adding new content and updating existing content to a central repository. This is well-founded if staff in the US must call into a central repository in the UK on a day-to-day basis to add content.
One possible solution is to use a distributed cluster with a Alfresco node in each office managing a repository cache that is synchronised with a central repository server. However, if I understand the architecture properly when a user adds new content the local node must still make a call to the central repository to ensure that there are no concurrency issues that may arise say from a user at another office simultaneously adding the same content or updating the same content. As an aside I would appreciate any links to more information about how Alfresco deals with concurrency issues.
Another approach would be to have independent Alfresco instances that implement some kind of bi-directional synchronisation between each other - but this again seems to lead to issues regarding conflict and resolution.
So my question really is has anybody had similar issues and what solution did they implement? Can Alfresco deal with this and if so, how? (any links to existing documentation to support this would be great).
Really appreciate any advice on this.
Thanks,
David
