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. Our first point is that NoSQL systems come in many flavors and it’s not just about key/value stores. These flavors include: Key/value stores (e.g., Hadoop) Document databases (e.g., MarkLogic, CouchDB) Graph databases (e.g., AllegroGraph) Distributed caching systems (e.g., Memcached) Our second point is that NoSQL is part of a broader trend in database systems : specialization. The jack-of-all-trades relational database (e.g., Oracle, DB2) works reasonably well for a broad range of applications — but it is a master of none. For any specific application, you can design a specialized DBMS that will outperform Oracle by 10 to 1000 times. Specialization represents, in aggregate, the biggest threat to the big-three DBMS oligopolists. Examples of specialized DBMSs include: Streambase, Skyler: real-time stream processing MarkLogic: semi-structured data Vertica, Greenplum: mid-range data warehousing Aster: large-scale (aka “big data”) analytic data warehousing VoltDB: high volume transaction processing MATLAB: scientific data management Our third point is that NoSQL is largely orthogonal to specializatio n. There are specialized NoSQL databases (e.g., MarkLogic) and there are specialized SQL databases (e.g., Aster, Volt). The only case where I think there are zero examples is general-purpose NoSQL systems. While I’m sure many of the NoSQL crowd would argue that their systems can do everything, is anyone *really* going to run general ledger or opportunity management on Hadoop? I don’t think so
See the article here:
Six Thoughts on The NoSQL Movement