As anyone who’s visited planet Earth in the last year or so knows, the NoSQL (“Not Only SQL”) movement is rapidly gaining both momentum and mind share, despite a number of prominent detractors. Rather than entering into a lengthy debate on the general pros and cons of NoSQL technologies, I’d like to reflect on the possible applications of these technologies to the specific problems of content management, a use case that (to my mind) it seems particularly well suited to. I briefly scraped the surface of this topic in a prior post.
As discussed previously what is meant when we refer to a “CMS” varies quite significantly depending on the use case, and my initial focus will be on the impact of NoSQL on CMS’s that target the Web Content Management (WCM) use case, followed with a post on the impact of NoSQL on the Document Management (DM) use case.
Even within the seemingly narrow confines of WCM, we’re discussing (at least!) two different problem domains (Content Production Systems and Presentation Management Systems) that have markedly different requirements (and are arguably unrelated), and I’ll discuss the impact of NoSQL on each of these areas in turn.