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

System Properties Comparison Amazon Redshift vs. Bangdb 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

Converged and high performance database for device data, events, time series, document and graph

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

Relational DBMS

Document store
Graph DBMS
Time Series DBMS

Graph DBMS

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

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	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series 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

Website

aws.amazon.com/redshift

bangdb.com

dgraph.io

www.elastic.co/elasticsearch

www.esgyn.cn

Technical documentation

docs.aws.amazon.com/redshift

docs.bangdb.com

dgraph.io/docs

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

Developer

Amazon (based on PostgreSQL)

Sachin Sinha, BangDB

Dgraph Labs, Inc.

Elastic

Esgyn

Initial release

2012

2016

2010

2015

Current release

BangDB 2.0, October 2021

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

BSD 3

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

Java

C++, Java

Server operating systems

hosted

Linux

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

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL like support with command line tool

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

Proprietary protocol
RESTful HTTP API

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

C
C#
C++
Java
Python

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, Notifications (with Streaming only)

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor, Knob for CAP (enterprise version only)

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

Tunable consistency, set CAP knob accordingly

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

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes

yes, run db with in-memory only mode

Memcached and Redis integration

User concepts

Access control

fine grained access rights according to SQL-standard

yes (enterprise version only)

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.