DBMS > Snowflake vs. Splunk vs. Stardog vs. TerminusDB

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Analytics Platform for Big Data

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

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

Primary database model

Secondary database models

Document store
RDF store

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

Technical documentation

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

docs.stardog.com

terminusdb.github.io/terminusdb/#

Developer

Snowflake Computing Inc.

Splunk Inc.

Stardog-Union

DataChemist Ltd.

Initial release

2014

2003

2010

2018

Current release

7.3.0, May 2020

11.0.0, January 2023

License

Commercial or Open Source

commercial

Limited free edition and free developer edition available

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Java

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

Data scheme

yes

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

yes

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

SQL-like query language (WOQL)

APIs and other access methods

CLI Client
JDBC
ODBC

HTTP REST

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions and aggregates, HTTP Server extensions in Java

yes

Triggers

similar concept for controling cloud resources

yes

via event handlers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication in HA-Cluster

Journaling Streams

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 in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

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

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

User concepts

Access control

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.