DBMS > MarkLogic vs. Sphinx vs. Teradata Aster

System Properties Comparison MarkLogic vs. Sphinx vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	MarkLogic  Xexclude from comparison	Sphinx  Xexclude from comparison	Teradata Aster  Xexclude from comparison
			Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.
Description	Operational and transactional Enterprise NoSQL database	Open source search engine for searching in data from different sources, e.g. relational databases	Platform for big data analytics on multistructured data sources and types
Primary database model	Document store Native XML DBMS RDF store as of version 7 Search engine	Search engine	Relational DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 10.00 Rank #50   Overall #9   Document stores #1   Native XML DBMS #1   RDF stores #4   Search engines	Score 7.23 Rank #61   Overall #8   Search engines
Website	www.marklogic.com	sphinxsearch.com
Technical documentation	docs.marklogic.com	sphinxsearch.com/­docs
Developer	MarkLogic Corp.	Sphinx Technologies Inc.	Teradata
Initial release	2001	2001	2005
Current release	9.0, 2017	3.4.1, July 2021
License Commercial or Open Source	commercial restricted free version is available	Open Source GPL version 2, commercial licence available	commercial
Cloud-based only Only available as a cloud service	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	C++	C++
Server operating systems	Linux OS X Windows	FreeBSD Linux NetBSD OS X Solaris Windows	Linux
Data scheme	schema-free Schema can be enforced	yes	Flexible Schema (defined schema, partial schema, schema free) defined schema within the relational store; partial schema or schema free in the Aster File Store
Typing predefined data types such as float or date	yes	no	yes
XML support Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.	yes		yes in Aster File Store
Secondary indexes	yes	yes full-text index on all search fields	yes
SQL Support of SQL	yes SQL92	SQL-like query language (SphinxQL)	yes
APIs and other access methods	Java API Node.js Client API ODBC proprietary Optic API Proprietary Query API, introduced with version 9 RESTful HTTP API SPARQL WebDAV XDBC XQuery XSLT	Proprietary protocol	ADO.NET JDBC ODBC OLE DB
Supported programming languages	C C# C++ Java JavaScript (Node.js) Perl PHP Python Ruby	C++ unofficial client library Java Perl unofficial client library PHP Python Ruby unofficial client library	C C# C++ Java Python R
Server-side scripts Stored procedures	yes via XQuery or JavaScript	no	R packages
Triggers	yes	no	no
Partitioning methods Methods for storing different data on different nodes	Sharding	Sharding Partitioning is done manually, search queries against distributed index is supported	Sharding
Replication methods Methods for redundantly storing data on multiple nodes	yes	none	yes Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.
MapReduce Offers an API for user-defined Map/Reduce methods	yes via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs	no	yes SQL Map-Reduce Framework
Consistency concepts Methods to ensure consistency in a distributed system	Immediate Consistency		Immediate Consistency or Eventual Consistency depending on configuration
Foreign keys Referential integrity	no	no	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	ACID can act as a resource manager in an XA/JTA transaction	no	ACID
Concurrency Support for concurrent manipulation of data	yes	yes	yes
Durability Support for making data persistent	yes	yes The original contents of fields are not stored in the Sphinx index.	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes, with Range Indexes		no
User concepts Access control	Role-based access control at the document and subdocument levels	no	fine grained access rights according to SQL-standard
More information provided by the system vendor We invite representatives of system vendors to contact us for updating and extending the system information, and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.
Related products and services We invite representatives of vendors of related products to contact us for presenting information about their offerings here.
More resources
	MarkLogic	Sphinx	Teradata Aster
DB-Engines blog posts