Check the full post for some NoSQL insights from Mark Logic CEO Dave Kellogg. This will probably surprise him, but I agree with all of his insights; my main complaint about “NoSQL” is the name: since most information management work should be done in a mix of SQL and XQuery, it’s counterproductive to imply that SQL is somehow irrevocably broken just because it’s associated with traditional RDBMS products. I also found the earlier extended-relational-DBMSs-are-junk meme associated with the NoSQL “movement” frustrating, but that meme seems to have been quietly deemphasized lately, and replaced with a more diplomatic and constructive positioning model, as exemplified by Dave’s post.
We are in the middle of one of our periodic analyst tours at MarkLogic, where we meet about 50 top software industry analysts focused in areas like enterprise search, enterprise content management, and database management systems. The NoSQL movement was one of four key topics we are covering, and while I’d expected some lively discussions about it, most of the time we have found ourselves educating people about NoSQL.
In this post, I’ll share the six key points we’re making about NoSQL on the tour.