DBMS > Graph Engine vs. Microsoft SQL Server vs. Percona Server for MongoDB vs. TinkerGraph

System Properties Comparison Graph Engine vs. Microsoft SQL Server vs. Percona Server for MongoDB vs. TinkerGraph

Please select another system to include it in the comparison.

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

Microsofts flagship relational DBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Document store

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.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

www.graphengine.io

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

www.percona.com/mongodb/software/percona-server-for-mongodb

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

Technical documentation

www.graphengine.io/docs/manual

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

docs.percona.com/percona-distribution-for-mongodb

Developer

Microsoft

Percona

Initial release

2010

1989

2015

2009

Current release

SQL Server 2022, November 2022

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

GPL Version 2

Open Source

Apache 2.0

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

.NET and C

C++

Java

Server operating systems

.NET

Linux
Windows

Linux

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

yes

APIs and other access methods

RESTful HTTP API

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

proprietary protocol using JSON

TinkerPop 3

Supported programming languages

C#
C++
F#
Visual Basic

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Groovy
Java

Server-side scripts

Stored procedures

yes

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

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

none

Foreign keys

Referential integrity

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

via In-Memory Engine

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.