DBMS > GeoSpock vs. JaguarDB vs. SAP IQ vs. Snowflake vs. Splunk

System Properties Comparison GeoSpock vs. JaguarDB vs. SAP IQ vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be 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

Columnar RDBMS optimized for Big Data analytics

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

column-oriented

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

geospock.com

www.jaguardb.com

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

www.splunk.com

Technical documentation

www.jaguardb.com/support.html

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

GeoSpock

DataJaguar, Inc.

SAP, formerly Sybase

Snowflake Computing Inc.

Splunk Inc.

Initial release

2015

1994

2014

2003

Current release

2.0, September 2019

3.3 July 2023

16.1 SPS04, April 2019

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

Limited free edition and free developer edition available

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

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

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

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

SAP/Sybase Replication Server

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

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.

User concepts

Access control

Access rights for users can be defined per table

rights management via user accounts

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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