DBMS > gStore vs. MySQL vs. OrientDB vs. Rockset

System Properties Comparison gStore vs. MySQL vs. OrientDB vs. Rockset

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native Graph DBMS to store and maintain very large RDF datasets.

Widely used open source RDBMS

Multi-model DBMS (Document, Graph, Key/Value)

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Graph DBMS
RDF store

Relational DBMS

Key/Value like access via memcached API

Document store
Graph DBMS
Key-value store

Document store

Secondary database models

Document store
Spatial DBMS

Relational DBMS
Search engine

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

Score	0.03
Rank	#367	Overall
	#37	Graph DBMS
	#18	RDF stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	3.02
Rank	#88	Overall
	#16	Document stores
	#6	Graph DBMS
	#12	Key-value stores

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

Technical documentation

en.gstore.cn/#/enDocs

dev.mysql.com/doc

www.orientdb.com/docs/last/index.html

docs.rockset.com

Developer

Oracle

since 2010, originally MySQL AB, then Sun

OrientDB LTD; CallidusCloud; SAP

Rockset

Initial release

2016

1995

2010

2019

Current release

1.2, November 2023

9.0.0, July 2024

3.2.29, March 2024

License

Commercial or Open Source

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache version 2

commercial

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

C++

C and C++

Java

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java JDK (>= JDK 6)

hosted

Data scheme

schema-free and OWL/RDFS-schema support

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language, no joins

Read-only SQL queries, including JOINs

APIs and other access methods

HTTP API
SPARQL 1.1

ADO.NET
JDBC
ODBC
Proprietary native API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP REST

Supported programming languages

C++
Java
JavaScript (Node.js)
PHP
Python

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Java, Javascript

Triggers

yes

Hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

relationship in graphs

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

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

yes

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, roles and permissions, Role-Based Access Control (RBAC) supported

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles; record level security configurable

Access rights for users and organizations can be defined via Rockset console

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.