DBMS > GridDB vs. MarkLogic vs. Splunk vs. SQLite vs. Vertica

System Properties Comparison GridDB vs. MarkLogic vs. Splunk vs. SQLite vs. Vertica

Editorial information provided by DB-Engines

Name

Description

Scalable in-memory time series database optimized for IoT and Big Data

Operational and transactional Enterprise NoSQL database

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Time Series DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Search engine

Relational DBMS

Column oriented

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

Score	93.02
Rank	#13	Overall
	#2	Search engines

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	9.62
Rank	#42	Overall
	#26	Relational DBMS

Website

griddb.net

www.progress.com/marklogic

www.splunk.com

www.sqlite.org

www.vertica.com

Technical documentation

docs.griddb.net

www.progress.com/marklogic/documentation

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

vertica.com/documentation

Developer

Toshiba Corporation

MarkLogic Corp.

Splunk Inc.

Dwayne Richard Hipp

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2013

2001

2003

2000

2005

Current release

5.1, August 2022

11.0, December 2022

3.46.1 (13 August 2024), August 2024

12.0.3, January 2023

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

Open Source

Public Domain

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Linux

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

server-less

Linux

Data scheme

yes

schema-free

Schema can be enforced

yes

dynamic column types

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

not rigid because of 'dynamic typing' concept.

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL92

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

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

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

C#
Java
JavaScript
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication

none

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

yes

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

can act as a resource manager in an XA/JTA transaction

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

via file-system locks

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

yes, with Range Indexes

yes

User concepts

Access control

Access rights for users can be defined per database

Role-based access control at the document and subdocument levels

Access rights for users and roles

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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.