DBMS > Apache Doris vs. Riak KV vs. RocksDB vs. Solr

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An MPP-based analytics DBMS embracing the MySQL protocol

Distributed, fault tolerant key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Key-value store

Search engine

Secondary database models

Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.57
Rank	#244	Overall
	#113	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

doris.apache.org
github.com/apache/doris

rocksdb.org

solr.apache.org

Technical documentation

github.com/apache/doris/wiki

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

Apache Software Foundation, originally contributed from Baidu

OpenSource, formerly Basho Technologies

Facebook, Inc.

Apache Software Foundation

Initial release

2017

2009

2013

2006

Current release

1.2.2, February 2023

3.2.0, December 2022

8.11.4, April 2024

9.6.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

C++

Java

Server operating systems

Linux

Linux
OS X

Linux

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

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.

yes

Secondary indexes

yes

restricted

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

JDBC
MySQL client

HTTP API
Native Erlang Interface

C++ API
Java API

Java API
RESTful HTTP/JSON API

Supported programming languages

Java

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

C
C++
Go
Java
Perl
Python
Ruby

.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

Erlang

Java plugins

Triggers

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"

horizontal partitioning

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

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

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes, using Riak Security

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.