DBMS > Graph Engine vs. MySQL vs. Sequoiadb vs. Tibero

System Properties Comparison Graph Engine vs. MySQL vs. Sequoiadb vs. Tibero

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

Widely used open source RDBMS

NewSQL database with distributed OLTP and SQL

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
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	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.graphengine.io

www.mysql.com

www.sequoiadb.com

us.tmaxsoft.com/products/tibero

Technical documentation

www.graphengine.io/docs/manual

dev.mysql.com/doc

www.sequoiadb.com/en/index.php?m=Files&a=index

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Sequoiadb Ltd.

TmaxSoft

Initial release

2010

1995

2013

2003

Current release

8.4.0, April 2024

6, April 2015

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Server: AGPL; Client: Apache V2

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

.NET and C

C and C++

C++

C and Assembler

Server operating systems

.NET

FreeBSD
Linux
OS X
Solaris
Windows

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

with proprietary extensions

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C#
C++
F#
Visual Basic

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

.Net
C++
Java
PHP
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

proprietary syntax

JavaScript

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

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

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

Document is locked during a transaction

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

In-memory capabilities

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

yes

planned for next version

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

simple password-based access control

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.