DBMS > GeoSpock vs. JaguarDB vs. MySQL vs. Splunk vs. Trafodion

System Properties Comparison GeoSpock vs. JaguarDB vs. MySQL vs. Splunk vs. Trafodion

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Performant, highly scalable DBMS for AI and IoT applications

Widely used open source RDBMS

Analytics Platform for Big Data

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.03
Rank	#365	Overall
	#56	Key-value stores
	#17	Vector DBMS

Score	1017.80
Rank	#2	Overall
	#2	Relational DBMS

Score	88.47
Rank	#13	Overall
	#2	Search engines

Website

geospock.com

Technical documentation

www.jaguardb.com/support.html

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

trafodion.apache.org/documentation.html

Developer

GeoSpock

DataJaguar, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

Apache Software Foundation, originally developed by HP

Initial release

2015

1995

2003

2014

Current release

2.0, September 2019

3.3 July 2023

9.0.0, July 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPL V3.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 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Javascript

C++

the server part. Clients available in other languages

C and C++

C++, Java

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

Splunk Search Processing Language for search commands

yes

APIs and other access methods

JDBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Multi-source replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

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

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

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

Access rights for users can be defined per table

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

fine grained access rights according to SQL-standard

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.