DBMS > Google Cloud Datastore vs. HBase vs. Microsoft SQL Server vs. Snowflake vs. Splunk

System Properties Comparison Google Cloud Datastore vs. HBase vs. Microsoft SQL Server vs. Snowflake vs. Splunk

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Microsofts flagship relational DBMS

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

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

cloud.google.com/datastore

hbase.apache.org

www.microsoft.com/en-us/sql-server

www.snowflake.com

www.splunk.com

Technical documentation

cloud.google.com/datastore/docs

hbase.apache.org/book.html

learn.microsoft.com/en-US/sql/sql-server

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Snowflake Computing Inc.

Splunk Inc.

Initial release

2008

1989

2014

2003

Current release

2.3.4, January 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

restricted free version is available

commercial

Limited free edition and free developer edition 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

C++

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

Linux
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

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

yes, details here

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

SQL-like query language (GQL)

yes

Splunk Search Processing Language for search commands

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

yes

Coprocessors in Java

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

user defined functions

yes

Triggers

Callbacks using the Google Apps Engine

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

fine grained access rights according to SQL-standard

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

Access rights for users and 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.