CMIS - mitigating integration risks for your content
by Scott Davis
While consolidation efforts help to lend sanity to an IT portfolio, it's rare that anyone is able to collapse things into a single, unified stack covering all scenarios. Instead options become codified using a number of "pre approved" product sets in various categories: a key one being DM & WCM.
Each permutation carries different costs with respect to licensing, operating, and integrating the underlying components. The last point can lead to many unknowns in a project plan - exactly why CMIS was born and continues to evolve. CMIS, or Content Management Interoperability Services, provides a common 'language' that all DM and WCM repositories may 'speak' to each other. No more product-by-product API calls (read: custom code) to maintain but rather a single approach to control things, just as with SQL-92, upon which many aspects of the CMIS syntax were designed.
This mitigates much of the risk when assessing different combinations, especially where pre-packaged options and partnerships exist to leverage it. Joint Acquia and Alfresco customers have already figured this out, including:
- King Center - https://www.acquia.com/resources/case-study/king-center
- Mercy Health Systems - http://www.alfresco.com/customers/mercy-health-systems
Perfect examples of end-to-end open source innovation in action.