In the course of doing some work for one of our partners – we were asked to take a look at the existing workload for their ECM team. This particular ECM team has done a great job maintaining and integrating ECM components from a variety of vendors. As typical in such an environment – we found that everyone on the team had primary support duties for at least one component, and was involved in customer support issues or updating /enhancing one or more of the company’s ECM products on pretty much a daily basis. Continue reading
We’re going to add one more item to our pre-ECM project checklist:
1) Where should we store our content?
Database storage used to be expensive. In the 1950’s, the cost per megabyte of storage exceeded $10,000/MB. Today, the cost has dropped to a few cents. Not only have storage costs dropped, so have memory costs as they have followed the same price drop as storage. Taking advantage of lower costs; most DB manufacturers have begun offering high performance in memory databases (IMDB – In-Memory Database).
From an ECM perspective; because of the higher database costs, content storage solutions were designed to use databases to store only the metadata or the index values associated with content, and the actual files and documents were stored on cheaper file storage devices. While lowering costs, this approach meant that ECM solutions were forced with managing, synchronizing, backing up, and designing applications where index values were one place and the actual documents, audio/video files were somewhere else.Continue reading