DBMS > Graphite vs. Microsoft SQL Server vs. TinkerGraph vs. VoltDB

System Properties Comparison Graphite vs. Microsoft SQL Server vs. TinkerGraph vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Microsofts flagship relational DBMS

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

github.com/graphite-project/graphite-web

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

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

www.voltdb.com

Technical documentation

graphite.readthedocs.io

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

docs.voltdb.com

Developer

Chris Davis

Microsoft

VoltDB Inc.

Initial release

2006

1989

2009

2010

Current release

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Python

C++

Java

Java, C++

Server operating systems

Linux
Unix

Linux
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

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

only a subset of SQL 99

APIs and other access methods

HTTP API
Sockets

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

TinkerPop 3

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

JavaScript (Node.js)
Python

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

Groovy
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

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

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

optional

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.