DBMS > Dolt vs. Elasticsearch vs. OpenEdge vs. RocksDB

System Properties Comparison Dolt vs. Elasticsearch vs. OpenEdge vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Application development environment with integrated database management system

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

Primary database model

Secondary database models

Document store

Document store
Spatial DBMS
Vector DBMS

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

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

Website

github.com/dolthub/dolt
www.dolthub.com

www.elastic.co/elasticsearch

www.progress.com/openedge

rocksdb.org

Technical documentation

docs.dolthub.com

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

documentation.progress.com/output/ua/OpenEdge_latest

github.com/facebook/rocksdb/wiki

Developer

DoltHub Inc

Elastic

Progress Software Corporation

Facebook, Inc.

Initial release

2018

2010

1984

2013

Current release

8.6, January 2023

OpenEdge 12.2, March 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Elastic License

commercial

Open Source

BSD

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

C++

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

schema-free

Typing

predefined data types such as float or date

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

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

close to SQL 92

APIs and other access methods

CLI Client
HTTP REST

Java API
RESTful HTTP/JSON API

JDBC
ODBC

C++ API
Java API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

since Version 11.4

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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.

Memcached and Redis integration

yes

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

Users and groups

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.