DBMS > MarkLogic vs. Snowflake vs. Splunk vs. TerminusDB

System Properties Comparison MarkLogic vs. Snowflake vs. Splunk vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Operational and transactional Enterprise NoSQL database

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

Analytics Platform for Big Data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Search engine

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	6.50
Rank	#56	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#5	Search engines

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

Technical documentation

docs.marklogic.com

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

terminusdb.github.io/terminusdb/#

Developer

MarkLogic Corp.

Snowflake Computing Inc.

Splunk Inc.

DataChemist Ltd.

Initial release

2001

2014

2003

2018

Current release

11.0, December 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Limited free edition and free developer edition available

Open Source

GPL V3

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

C++

Prolog, Rust

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

Schema can be enforced

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

yes

SQL

Support of SQL

yes

SQL92

yes

Splunk Search Processing Language for search commands

SQL-like query language (WOQL)

APIs and other access methods

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

CLI Client
JDBC
ODBC

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

ACID

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

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, with Range Indexes

User concepts

Access control

Role-based access control at the document and subdocument levels

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

Access rights for users and roles

Role-based access control

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.