DBMS > Graph Engine vs. mSQL vs. Vitess vs. XTDB

System Properties Comparison Graph Engine vs. mSQL vs. Vitess vs. XTDB

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.graphengine.io

hughestech.com.au/products/msql

vitess.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.graphengine.io/docs/manual

vitess.io/docs

www.xtdb.com/docs

Developer

Microsoft

Hughes Technologies

The Linux Foundation, PlanetScale

Juxt Ltd.

Initial release

2010

1994

2013

2019

Current release

4.4, October 2021

15.0.2, December 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT License

commercial

free licenses can be provided

Open Source

Apache Version 2.0, commercial licenses available

Open Source

MIT License

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

.NET and C

Clojure

Server operating systems

.NET

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

Docker
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

C#
C++
F#
Visual Basic

C
C++
Delphi
Java
Perl
PHP
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Trinity
30 October 2010, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

The graph analytics landscape 2019
27 February 2019, Data Science Central

provided by Google News

A Brief History of PHP - Programming PHP, 3rd Edition [Book]
22 September 2018, O'Reilly Media

provided by Google News

Deepthi Sigireddi on Distributed Database Architecture in the Cloud Native Era
20 May 2024, InfoQ.com

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

CNCF’s Vitess Scales MySQL with the Help of Kubernetes
9 February 2018, The New Stack

provided by Google News

Share this page