[OASIS Issue Tracker] (CMIS-758) Discussion of more powerful batch operations for next version

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/CMIS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37850#comment-37850 ] 

Jay Brown commented on CMIS-758:
--------------------------------

Devils Advocate: I would like to float a polar opposite view of the batch scenario.  I submit that in the case where a an application needed to consume CMIS documents on a truly *massive* scale what we have today is more appropriate than a batch retrieve like I have previously described in this record.

First off, since CMIS servers are stateless by design,  they lend themselves to be deployed in clusters.  This is something that is frequently done in the case of FileNet’s CMIS servers.   
Assume you have this type of scenario which in the case of the largest installations may often be the case.   

Now to the client.   
If you had to process (say) 1 million documents that were in a CMIS repository; how would you do it? You would probably break up the problem into a million parallelizable parts and have a swarm of N processors attack the problem one doc at a time. (e.g. Hadoop like)   Thus you can scale. 

So do we really need batch retrieve (and create) in an era of massively parallel systems? 
Or is it still helpful enough for simple single threaded (UI) systems to have this redundancy?


> Discussion of more powerful batch operations for next version
> -------------------------------------------------------------
>
>                 Key: CMIS-758
>                 URL: https://tools.oasis-open.org/issues/browse/CMIS-758
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Jay Brown
>
> Creating this record as a placeholder for discussions on this subject. 
> What additional batch features should we support in v.next? (e.g.  batch Create, Delete, ...) 
> What should they look like? etc. 
> Please comment.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)