DBMS > Amazon Redshift vs. Cachelot.io vs. Dgraph vs. Elasticsearch vs. EsgynDB

System Properties Comparison Amazon Redshift vs. Cachelot.io vs. Dgraph vs. Elasticsearch vs. EsgynDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

In-memory caching system

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

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.00
Rank	#396	Overall
	#64	Key-value stores

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Website

aws.amazon.com/redshift

cachelot.io

dgraph.io

www.elastic.co/elasticsearch

www.esgyn.cn

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

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

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

Elastic

Esgyn

Initial release

2012

2015

2016

2010

2015

Current release

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Simplified BSD License

Open Source

Apache 2.0

Open Source

Elastic License

commercial

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

C++

Java

C++, Java

Server operating systems

hosted

FreeBSD
Linux
OS X

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

APIs and other access methods

JDBC
ODBC

Memcached protocol

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

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

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

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Synchronous replication via Raft

yes

Multi-source replication between multi datacenters

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

none

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

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

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.