DBMS > Dgraph vs. EsgynDB vs. Ignite vs. Microsoft SQL Server vs. TimesTen

System Properties Comparison Dgraph vs. EsgynDB vs. Ignite vs. Microsoft SQL Server vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Microsofts flagship relational DBMS

In-Memory RDBMS compatible to Oracle

Primary database model

Graph DBMS

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

dgraph.io

www.esgyn.cn

ignite.apache.org

www.microsoft.com/en-us/sql-server

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

dgraph.io/docs

apacheignite.readme.io/docs

learn.microsoft.com/en-US/sql/sql-server

docs.oracle.com/database/timesten-18.1

Developer

Dgraph Labs, Inc.

Esgyn

Apache Software Foundation

Microsoft

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2016

2015

1989

1998

Current release

Apache Ignite 2.6

SQL Server 2022, November 2022

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

commercial

restricted free version is 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

C++, Java

C++, Java, .Net

C++

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

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

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

Java Stored Procedures

yes (compute grid and cache interceptors can be used instead)

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

PL/SQL

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes (replicated cache)

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

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

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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.