One of the highlights of the D6.5 release was the new features around enabling high volumes of content in the repository. There are two standard problems around storing lots and lots of content in an ECM system.
- Every object in an ECM system has overhead. In Documentum, it is takes 2-3K in database storage per object. That can add up quick. Just think of the emails in your organization or the images that a financial institution might generate from scanned documents.
- The very act of adding content into the Content Server takes several round trips to the database. Is this a valid ACL to assign? Does the containing folder exist? Those are just two of the questions asked during the process.
After learning about these features in more detail, in discussions with Victor (See a recording of his presentation on the Developer Network) and Ed, at EMC World 2008, I started making plans to use it on one of my projects. I later learned that there is a catch. Before we get to the catch, let’s review the highlights.