DBMS > IBM Db2 warehouse vs. Lovefield vs. Snowflake vs. Splunk vs. SQream DB

System Properties Comparison IBM Db2 warehouse vs. Lovefield vs. Snowflake vs. Splunk vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

Cloud-based data warehousing service

Embeddable relational database for web apps written in pure JavaScript

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

Analytics Platform for Big Data

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Search engine

Relational DBMS

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

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

www.ibm.com/products/db2/warehouse

google.github.io/lovefield

www.snowflake.com

www.splunk.com

sqream.com

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

docs.sqream.com

Developer

IBM

Google

Snowflake Computing Inc.

Splunk Inc.

SQream Technologies

Initial release

2014

2003

2017

Current release

2.1.12, February 2017

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

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

JavaScript

C++, CUDA, Haskell, Java, Scala

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

yes

Splunk Search Processing Language for search commands

yes

APIs and other access methods

.NET Client API
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

HTTP REST

.Net
JDBC
ODBC

Supported programming languages

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

JavaScript

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

PL/SQL, SQL PL

user defined functions

yes

user defined functions in Python

Triggers

yes

Using read-only observers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Multi-source replication

none

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

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

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.