DBMS > Elasticsearch vs. MySQL vs. TerarkDB vs. VelocityDB

System Properties Comparison Elasticsearch vs. MySQL vs. TerarkDB vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Search engine

Relational DBMS

Key/Value like access via memcached API

Key-value store

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Spatial DBMS

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

Score	128.79
Rank	#8	Overall
	#1	Search engines

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	0.00
Rank	#385	Overall
	#40	Graph DBMS
	#21	Object oriented DBMS

Website

www.elastic.co/elasticsearch

www.mysql.com

github.com/bytedance/terarkdb

velocitydb.com

Technical documentation

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

dev.mysql.com/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

velocitydb.com/UserGuide

Developer

Elastic

Oracle

since 2010, originally MySQL AB, then Sun

ByteDance, originally Terark

VelocityDB Inc

Initial release

2010

1995

2016

2011

Current release

8.6, January 2023

9.0.0, July 2024

7.x

License

Commercial or Open Source

Open Source

Elastic License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted open source version available

commercial

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 and C++

C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Any that supports .NET

Data scheme

schema-free

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

yes

schema-free

yes

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

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

.Net

Supported programming languages

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

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

C++
Java

.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

by using the 'percolation' feature

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Based on Windows Authentication

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.