DBMS > Kingbase vs. MySQL vs. Neo4j vs. Tarantool

System Properties Comparison Kingbase vs. MySQL vs. Neo4j vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Widely used open source RDBMS

Scalable, ACID-compliant graph database designed with a high-performance distributed cluster architecture, available in self-hosted and cloud offerings

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.45
Rank	#262	Overall
	#123	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	44.46
Rank	#23	Overall
	#1	Graph DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

Technical documentation

dev.mysql.com/doc

neo4j.com/docs

www.tarantool.io/en/doc

Developer

BeiJing KINGBASE Information technologies inc.

Oracle

since 2010, originally MySQL AB, then Sun

Neo4j, Inc.

Initial release

1999

1995

2007

2008

Current release

V8.0, August 2021

8.4.0, April 2024

5.19, April 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL version3, commercial licenses available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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.

Neo4j Aura: Neo4j’s fully managed cloud service: The zero-admin, always-on graph database for cloud developers.

Implementation language

C and Java

C and C++

Java, Scala

C and C++

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Can also be used server-less as embedded Java database.
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

yes

schema-free and schema-optional

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

pluggable indexing subsystem, by default Apache Lucene

yes

SQL

Support of SQL

Standard with numerous extensions

yes

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

ADO.NET
JDBC
ODBC
Proprietary native API

Bolt protocol
Cypher query language
Java API
Neo4j-OGM

Object Graph Mapper
RESTful HTTP API
Spring Data Neo4j
TinkerPop 3

Open binary protocol

Supported programming languages

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
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
Clojure
Elixir
Go
Groovy
Haskell
Java
JavaScript
Perl
PHP
Python
Ruby
Scala

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

User defined Procedures and Functions

Lua, C and SQL stored procedures

Triggers

yes

via event handler

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes using Neo4j Fabric

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Causal Clustering using Raft protocol

available in in Enterprise Version only

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Causal and Eventual Consistency configurable in Causal Cluster setup
Immediate Consistency in stand-alone mode

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Users, roles and permissions. Pluggable authentication with supported standards (LDAP, Active Directory, Kerberos)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

Neo4j delivers graph technology that has been battle tested for performance and scale...
» more

Competitive advantages

Neo4j is the market leader, graph database category creator, and the most widely...
» more

Typical application scenarios

Real-Time Recommendations Master Data Management Identity and Access Management Network...
» more

Key customers

Over 800 commercial customers and over 4300 startups use Neo4j. Flagship customers...
» more

Market metrics

Neo4j boasts the world's largest graph database ecosystem with more than 140 million...
» more

Licensing and pricing models

GPL v3 license that can be used all the places where you might use MySQL. Neo4j Commercial...
» more

News

This Week in Neo4j: Podcast, GraphRAG, GraphQL, Chatbot and more
18 May 2024

Neo4j Joins the Connect with Confluent Partner Program
16 May 2024

10 Inspiring Projects to Spark Your NODES 2024 Presentation
15 May 2024

New Security Feature in Neo4j Aura: Customer Managed Keys
15 May 2024

Safeguarding Elections: How Graph Technology Powers Groundbreaking Research on Political Ads
13 May 2024

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.