DBMS > Apache Doris vs. Riak KV vs. Solr

System Properties Comparison Apache Doris vs. Riak KV vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Apache Doris  Xexclude from comparison	Riak KV  Xexclude from comparison	Solr  Xexclude from comparison
Description	An MPP-based analytics DBMS embracing the MySQL protocol	Distributed, fault tolerant key-value store	A widely used distributed, scalable search engine based on Apache Lucene
Primary database model	Relational DBMS	Key-value store with links between data sets and object tags for the creation of secondary indexes	Search engine
Secondary database models			Spatial DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 0.27 Rank #273   Overall #127   Relational DBMS	Score 6.52 Rank #65   Overall #9   Key-value stores	Score 56.61 Rank #20   Overall #3   Search engines
Website	doris.apache.org github.com/­apache/­doris	riak.com/­products/­riak-kv	lucene.apache.org/­solr
Technical documentation	github.com/­apache/­doris/­wiki		lucene.apache.org/­solr/­resources.html
Developer	Apache Software Foundation, originally contributed from Baidu	Basho Technologies	Apache Software Foundation
Initial release	2017	2009	2006
Current release	0.14, May 2021	2.1.0, April 2015	9.0.0, May 2022
License Commercial or Open Source	Open Source Apache Version 2.0	Open Source Apache version 2, commercial enterprise edition	Open Source Apache Version 2
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	Java	Erlang	Java
Server operating systems	Linux	Linux OS X	All OS with a Java VM runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)
Data scheme	yes	schema-free	yes Dynamic Fields enables on-the-fly addition of new fields
Typing predefined data types such as float or date	yes	no	yes supports customizable data types and automatic typing
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.	no	no	yes
Secondary indexes	yes	restricted	yes All search fields are automatically indexed
SQL Support of SQL	yes	no	Solr Parallel SQL Interface
APIs and other access methods	JDBC MySQL client	HTTP API Native Erlang Interface	Java API RESTful HTTP/JSON API
Supported programming languages	Java	C unofficial client library C# C++ unofficial client library Clojure unofficial client library Dart unofficial client library Erlang Go unofficial client library Groovy unofficial client library Haskell unofficial client library Java JavaScript unofficial client library Lisp unofficial client library Perl unofficial client library PHP Python Ruby Scala unofficial client library Smalltalk unofficial client library	.Net Erlang Java JavaScript any language that supports sockets and either XML or JSON Perl PHP Python Ruby Scala
Server-side scripts Stored procedures	user defined functions	JavaScript and Erlang	Java plugins
Triggers	no	yes pre-commit hooks and post-commit hooks	yes User configurable commands triggered on index changes
Partitioning methods Methods for storing different data on different nodes	horizontal partitioning	Sharding no "single point of failure"	Sharding
Replication methods Methods for redundantly storing data on multiple nodes	none	selectable replication factor	yes
MapReduce Offers an API for user-defined Map/Reduce methods	no	yes	spark-solr: github.com/­lucidworks/­spark-solr and streaming expressions to reduce
Consistency concepts Methods to ensure consistency in a distributed system	Immediate Consistency	Eventual Consistency	Eventual Consistency
Foreign keys Referential integrity	no	no links between data sets can be stored	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data		no	optimistic locking
Concurrency Support for concurrent manipulation of data	yes	yes	yes
Durability Support for making data persistent	yes	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	no		yes
User concepts Access control	fine grained access rights according to SQL-standard	no	yes
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
	Apache Doris	Riak KV	Solr
DB-Engines blog posts