DBMS > AgensGraph vs. MySQL vs. Splunk vs. Warp 10

System Properties Comparison AgensGraph vs. MySQL vs. Splunk vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

Analytics Platform for Big Data

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

Primary database model

Graph DBMS
Relational 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.17
Rank	#320	Overall
	#29	Graph DBMS
	#143	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	0.06
Rank	#351	Overall
	#35	Time Series DBMS

Website

bitnine.net/agensgraph

www.mysql.com

www.splunk.com

www.warp10.io

Technical documentation

bitnine.net/documentation

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

www.warp10.io/content/02_Getting_started

Developer

Bitnine Global Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

SenX

Initial release

2016

1995

2003

2015

Current release

2.1, December 2018

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Limited free edition and free developer edition 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.

Implementation language

C and C++

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

depending on used data model

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

SQL

Support of SQL

yes

with proprietary extensions

Splunk Search Processing Language for search commands

APIs and other access methods

Cypher Query Language
JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

HTTP API
Jupyter
WebSocket

Supported programming languages

C
Java
JavaScript
Python

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

C#
Java
JavaScript
PHP
Python
Ruby

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and 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.