What Distinguishes MarkLogic Server from Other NoSQL Alternatives?
While MarkLogic is like these systems in someways, it is quite distinct in others. At a high-level, MarkLogic is distinguished by
* Focus on intra-cluster consistency and ACID transactions
* Use of the XML data model
Fundamentally MarkLogic is designed and optimized to store, index, update, and search XML data. MarkLogic can also store plain text, JSON, and binaries data as well. But MarkLogic is optimized for XML. And as much as JSON is simpler and ideal for interaction with web browsers, XML still reigns supreme when dealing with structured documents that contain lots of text.
* The MarkLogic Universal Index
Because MarkLogic is based on a real-time search-engine core, we index the structure (elements, attributes, hierarchy) of documents as well as the full text. In MarkLogic, you can compose meaningful queries for semi-structured (or un-structured) data - the kind of data that is most prevalent in the real world. And you can do this without having to bolt on separate processes or separate pieces of technology (e.g. Lucene, SOLR). And because MarkLogic is also focused on ACID, every document insert or update results in a fully-transactional update of the index as well. The query results are always based exactly on what's currently in the database.