DBMS > HBase vs. Snowflake vs. Splunk vs. Vitess

System Properties Comparison HBase vs. Snowflake vs. Splunk vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Analytics Platform for Big Data

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

Technical documentation

hbase.apache.org/book.html

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

vitess.io/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Snowflake Computing Inc.

Splunk Inc.

The Linux Foundation, PlanetScale

Initial release

2008

2014

2003

2013

Current release

2.3.4, January 2021

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 2.0, commercial licenses 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

Server operating systems

Linux
Unix
Windows

using Cygwin

hosted

Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

schema-free, schema definition possible

yes

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

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
Thrift

CLI Client
JDBC
ODBC

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Coprocessors in Java

user defined functions

yes

proprietary syntax

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or 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.