DBMS > Graph Engine vs. JaguarDB vs. Microsoft Azure Synapse Analytics vs. Microsoft SQL Server vs. TinkerGraph

System Properties Comparison Graph Engine vs. JaguarDB vs. Microsoft Azure Synapse Analytics vs. Microsoft SQL Server vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Performant, highly scalable DBMS for AI and IoT applications

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Microsofts flagship relational DBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Graph DBMS
Key-value store

Key-value store
Vector DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

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

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

www.graphengine.io

www.jaguardb.com

azure.microsoft.com/services/synapse-analytics

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

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

www.graphengine.io/docs/manual

www.jaguardb.com/support.html

docs.microsoft.com/azure/synapse-analytics

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

Developer

Microsoft

DataJaguar, Inc.

Microsoft

Initial release

2010

2015

2016

1989

2009

Current release

3.3 July 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL V3.0

commercial

restricted free version is available

Open Source

Apache 2.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

.NET and C

C++

the server part. Clients available in other languages

C++

Java

Server operating systems

.NET

Linux

hosted

Linux
Windows

Data scheme

yes

schema-free

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC

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

TinkerPop 3

Supported programming languages

C#
C++
F#
Visual Basic

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

C#
Java
PHP

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

Groovy
Java

Server-side scripts

Stored procedures

yes

Transact SQL

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Sharding, horizontal partitioning

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

yes

Relationships in graphs

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

optional

In-memory capabilities

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

yes

User concepts

Access control

rights management via user accounts

yes

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.