DBMS > SingleStore vs. Snowflake vs. TerminusDB vs. Transwarp KunDB

System Properties Comparison SingleStore vs. Snowflake vs. TerminusDB vs. Transwarp KunDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

Document store
RDF store

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

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Score	0.04
Rank	#362	Overall
	#154	Relational DBMS

Website

www.singlestore.com

www.snowflake.com

terminusdb.com

www.transwarp.cn/en/product/kundb

Technical documentation

docs.singlestore.com

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

SingleStore Inc.

Snowflake Computing Inc.

DataChemist Ltd.

Transwarp

Initial release

2013

2014

2018

Current release

8.5, January 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

free developer edition available

commercial

Open Source

GPL V3

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++, Go

Prolog, Rust

Server operating systems

Linux

64 bit version required

hosted

Linux

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

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

but no triggers and foreign keys

yes

SQL-like query language (WOQL)

yes

APIs and other access methods

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Bash
C
C#
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

hash partitioning

yes

Graph Partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

stores two copies of each physical data partition on two separate nodes

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes

in-memory journaling

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

Fine grained access control via users, groups and roles

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

Role-based access control

yes

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.