Hello All,
We are planning to use Documentum CMIS for CRUD operations. Are there some additional overheads/Maintenance/IT costs involved that might be important to consider for deciding between CMIS and DFS?
feature wise: dfs has more (specific) features than cmis (cmis is a standard an only provides standard features)
maintenance (coding): dfs requires knowledge about DFS (soap only) api while cmis is a soap/rest framework, which makes it "easier" to mantain (and you have apache chemistry to make things even easier)
IMHO, the way to go (from best to worst) is REST -> CMIS -> DFS
DFS, CMIS, and REST have different perspective. If only talking about the server performance overhead, there is no much difference since the service layer is thin.
Some questions we need to ask when we consider a new API adoption.
These questions may help you to make the decision.
Regards,
William
I agree with Alvaro. Documentum's REST API has many more features than CMIS, and we've had very good feedback from programmers. The overhead of CMIS or REST should be very similar. DFS has some features that are not yet in the current REST API, but requires you to use SOAP rather than REST. Most programmers prefer REST. So the Documentum REST API is the sweet spot for a lot of programmers.
William just posted, our posts basically agree. As he points out, CMIS is mostly for compatibility with other vendors. And extensibility can be really important for many applications, for that you want REST or DFS, and REST even allows you to use extensibility to add new authentication mechanisms.
Hi All,
Does CMIS invokes TBO functions like DFS does ?
Thanks
DFS development requires obsolete / out of support Java versions
