DBMS > Amazon Redshift vs. Dgraph vs. Elasticsearch vs. EsgynDB vs. JaguarDB

System Properties Comparison Amazon Redshift vs. Dgraph vs. Elasticsearch vs. EsgynDB vs. JaguarDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed and scalable native Graph DBMS

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Key-value store
Vector DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Website

aws.amazon.com/redshift

dgraph.io

www.elastic.co/elasticsearch

www.esgyn.cn

www.jaguardb.com

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

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

www.jaguardb.com/support.html

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

Elastic

Esgyn

DataJaguar, Inc.

Initial release

2012

2016

2010

2015

Current release

8.6, January 2023

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Elastic License

commercial

Open Source

GPL V3.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++, Java

C++

the server part. Clients available in other languages

Server operating systems

hosted

Linux
OS X
Windows

All OS with a Java VM

Linux

Data scheme

yes

schema-free

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

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.

Secondary indexes

restricted

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Java Stored Procedures

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

yes

Multi-source replication between multi datacenters

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

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

Memcached and Redis integration

User concepts

Access control

fine grained access rights according to SQL-standard

Planned for future releases

fine grained access rights according to SQL-standard

rights management via user accounts

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.