DBMS > JaguarDB vs. Snowflake vs. SQream DB vs. TerarkDB vs. Transbase

System Properties Comparison JaguarDB vs. Snowflake vs. SQream DB vs. TerarkDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

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

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Key-value store
Vector DBMS

Relational DBMS

Key-value store

Relational DBMS

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

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

www.jaguardb.com

www.snowflake.com

sqream.com

github.com/bytedance/terarkdb

www.transaction.de/en/products/transbase.html

Technical documentation

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

docs.sqream.com

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.transaction.de/en/products/transbase/features.html

Developer

DataJaguar, Inc.

Snowflake Computing Inc.

SQream Technologies

ByteDance, originally Terark

Transaction Software GmbH

Initial release

2015

2014

2017

2016

1987

Current release

3.3 July 2023

2022.1.6, December 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPL V3.0

commercial

restricted open source version available

commercial

free development license

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

the server part. Clients available in other languages

C++, CUDA, Haskell, Java, Scala

C++

C and C++

Server operating systems

Linux

hosted

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC
ODBC

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

C++
Java

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

user defined functions in Python

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal and vertical partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

rights management via user accounts

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

fine grained access rights according to SQL-standard

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.