DBMS > BaseX vs. Graph Engine vs. Kinetica vs. MySQL

System Properties Comparison BaseX vs. Graph Engine vs. Kinetica vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Fully vectorized database across both GPUs and CPUs

Widely used open source RDBMS

Primary database model

Native XML DBMS

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

docs.basex.org

www.graphengine.io/docs/manual

docs.kinetica.com

dev.mysql.com/doc

Developer

BaseX GmbH

Microsoft

Kinetica

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2007

2010

2012

1995

Current release

11.0, June 2024

7.1, August 2021

8.4.0, April 2024

License

Commercial or Open Source

Open Source

BSD license

Open Source

MIT License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

.NET and C

C, C++

C and C++

Server operating systems

Linux
OS X
Windows

.NET

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

XQuery supports types

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

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

C#
C++
F#
Visual Basic

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

user defined functions

yes

proprietary syntax

Triggers

yes

via events

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

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 or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

multiple readers, single writer

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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

GPU vRAM or System RAM

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Access rights for users and roles on table level

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.