Aug 142012
 

I am a solutions engineer for Alfresco Software covering the northeastern United States. As such, I believe it is important to clearly communicate the many ways in which our enterprise content management platform can be used in the financial services industry, which is very prevalent in the northeast. Therefore, I have done some research on current customer use cases as well as potential use cases discovered from a few sources.  Namely, the annual reports of some of the biggest banks in the world, and discussions with several colleagues internally and at some of our partner companies. One of those partners agreed to work with me to flesh out the bits and bytes to be able to demonstrate one of the use cases, and so of course I created a site in Alfresco’s cloud at http://my.alfresco.com and invited a few folks from the partner company to join and collaborate with me there.  I uploaded the document in which I was collecting use case research, and another that included details of the design for the first use case.

And therein lies the problem.

Both of those documents were already in their own folder within our U.S. Solutions Engineering Share site in our on-premise deployment of Alfresco, because I’ve been collaborating with some of my colleagues on them as well.  Now I’m collaborating with two different groups of people on the same documents, and I have to carefully manage updates in both directions.  This is why I need Alfresco cloud sync.

Fortunately, Alfresco’s product management, engineering, quality assurance, and release management teams are inching ever closer to releasing this capability to the world, upon which time I will gladly begin to take advantage the automatic nature of Alfresco cloud sync.  I’ll set up synchronization of the folder containing the two documents within our on-premise deployment of Alfresco with the document library of the site I created in the Alfresco cloud to collaborate with our partners.  And forever after, I can collaborate on this project seamlessly both internally and externally while maintaining changes and versions from both places.

Seriously, how cool is that?

 

  3 Responses to “Why I Need Alfresco Cloud Sync”

  1. Hallo Brian,

    I fully understand the need to address the sychronization issue, but two-way-sync in general is not an easy problem to solve. I wonder how you guys will deal with the conflict situation.

    Anyways, two-way-sync definitely is an awesome feature.

    regards
    Andreas

  2. Hi Andreas,

    As I understand it, sync will occur every minute (the on-premise installation will poll the cloud for changes). In the (unlikely) event of a conflict, when changes have occurred on premise as well as in the cloud during that minute, the cloud version will win, and will become the most current version of the document on-premise. This way, the on-premise user can compare the two versions (perhaps via Sharepoint protocol, leveraging Microsoft office’s “Compare Versions” capability), and resolve conflicts. That’s how I would do it at least.

    Of course, this is all subject to the normal disclaimer that I’m not part of Alfresco engineering or product management, so I might be completely misinformed. I’m sure there will be more details released once cloud sync becomes available though.

  3. You can learn more about Alfresco One here in this webinar (Using Alfresco’s Hybrid Cloud Architecture for Better Web Content Management) and see it in action applied to WCM use cases:

    https://www.facebook.com/crafter.studio.developers/posts/105307676327084?notif_t=like

 Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>