DBMS > AgensGraph vs. Dgraph vs. MySQL vs. Sphinx vs. Warp 10

System Properties Comparison AgensGraph vs. Dgraph vs. MySQL vs. Sphinx vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Distributed and scalable native Graph DBMS

Widely used open source RDBMS

Open source search engine for searching in data from different sources, e.g. relational databases

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Graph DBMS
Relational DBMS

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Search engine

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

bitnine.net/agensgraph

Technical documentation

bitnine.net/documentation

dgraph.io/docs

dev.mysql.com/doc

sphinxsearch.com/docs

www.warp10.io/content/02_Getting_started

Developer

Bitnine Global Inc.

Dgraph Labs, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Sphinx Technologies Inc.

SenX

Initial release

2016

1995

2001

2015

Current release

2.1, December 2018

8.4.0, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL version 2, commercial licence available

Open Source

Apache License 2.0

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

C and C++

C++

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

depending on used data model

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (SphinxQL)

APIs and other access methods

Cypher Query Language
JDBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

C
Java
JavaScript
Python

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

yes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication via Raft

Multi-source replication
Source-replica replication

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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

The original contents of fields are not stored in the Sphinx index.

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

fine grained access rights according to SQL-standard

Planned for future releases

Users with fine-grained authorization concept

no user groups or roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.