DBMS > Apache Phoenix vs. Snowflake vs. Splunk vs. TerminusDB vs. VelocityDB

System Properties Comparison Apache Phoenix vs. Snowflake vs. Splunk vs. TerminusDB vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Relational DBMS

Search engine

Graph DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Document store
RDF store

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

Technical documentation

phoenix.apache.org

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

terminusdb.github.io/terminusdb/#

velocitydb.com/UserGuide

Developer

Apache Software Foundation

Snowflake Computing Inc.

Splunk Inc.

DataChemist Ltd.

VelocityDB Inc

Initial release

2014

2003

2018

2011

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

11.0.0, January 2023

7.x

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Limited free edition and free developer edition available

Open Source

GPL V3

commercial

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

Linux
Unix
Windows

hosted

Linux
OS X
Solaris
Windows

Linux

Any that supports .NET

Data scheme

yes

late-bound, schema-on-read capabilities

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

Splunk Search Processing Language for search commands

SQL-like query language (WOQL)

APIs and other access methods

JDBC

CLI Client
JDBC
ODBC

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

.Net

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

JavaScript
Python

.Net

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication

Journaling Streams

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 or Eventual Consistency

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

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

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

Access rights for users and roles

Role-based access control

Based on Windows Authentication

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.