DBMS > Google Cloud Datastore vs. IBM Db2 vs. SAP SQL Anywhere vs. Snowflake vs. Splunk

System Properties Comparison Google Cloud Datastore vs. IBM Db2 vs. SAP SQL Anywhere 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

Common in IBM host environments, 2 different versions for host and Windows/Linux

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Analytics Platform for Big Data

Primary database model

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Search engine

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	127.49
Rank	#8	Overall
	#5	Relational DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

cloud.google.com/datastore

www.ibm.com/products/db2

www.sap.com/products/technology-platform/sql-anywhere.html

www.snowflake.com

www.splunk.com

Technical documentation

cloud.google.com/datastore/docs

www.ibm.com/docs/en/db2

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Google

IBM

SAP

formerly Sybase

Snowflake Computing Inc.

Splunk Inc.

Initial release

2008

1983

host version

1992

2014

2003

Current release

12.1, October 2016

17, July 2015

License

Commercial or Open Source

commercial

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

C and C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes, details here

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

yes

yes, in C/C++, Java, .Net or Perl

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

only with Windows/Unix/Linux Version

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

with separate tools (MQ, InfoSphere)

Source-replica replication

Database mirroring

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

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

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)

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.