This is the first of two sessions by Ed Bueche. His sessions are must-attends. His sessions last year, part one and part two, are useful references, but as always, this year’s information takes precedence. Some information that Ed is presenting is available in the Architecture session notes.
Victor Spivak, chief architect for the platform, is presenting on what is the most popular topic post from last year. Victor is smart and doesn’t mince words. The session was mostly packed 15 minutes before it even started.
Victor is going to breeze through many of the things that haven’t changed in a year, so supplement these notes with last year’s notes. These notes are “more accurate” if they conflict.
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.
Time for an update on the architecture. Victor Spivak is presenting. He knows his stuff, so hopefully it’ll be a good one. I know waaay too many people in this room. I’ll never get to say hello to all of them. This is by far the most crowded session.