DBMS > Kinetica vs. MarkLogic vs. Snowflake vs. SQream DB

System Properties Comparison Kinetica vs. MarkLogic vs. Snowflake vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

Operational and transactional Enterprise NoSQL database

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

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

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	6.50
Rank	#56	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#5	Search engines

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.73
Rank	#228	Overall
	#105	Relational DBMS

Website

Technical documentation

docs.kinetica.com

docs.marklogic.com

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

Kinetica

MarkLogic Corp.

Snowflake Computing Inc.

SQream Technologies

Initial release

2012

2001

2014

2017

Current release

7.1, August 2021

11.0, December 2022

2022.1.6, December 2022

License

Commercial or Open Source

commercial

restricted free version is 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

C, C++

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux

Linux
OS X
Windows

hosted

Linux

Data scheme

yes

schema-free

Schema can be enforced

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL92

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

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

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

via XQuery or JavaScript

user defined functions

user defined functions in Python

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

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

GPU vRAM or System RAM

yes, with Range Indexes

User concepts

Access control

Access rights for users and roles on table level

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept, user roles and pluggable 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.