DBMS > SiriDB vs. Snowflake vs. TerminusDB vs. VelocityDB vs. Vitess

System Properties Comparison SiriDB vs. Snowflake vs. TerminusDB vs. VelocityDB vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Open Source Time Series DBMS

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Time Series DBMS

Relational DBMS

Graph DBMS

Graph DBMS
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
RDF store

Document store
Spatial DBMS

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

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

Technical documentation

docs.siridb.com

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

velocitydb.com/UserGuide

vitess.io/docs

Developer

Cesbit

Snowflake Computing Inc.

DataChemist Ltd.

VelocityDB Inc

The Linux Foundation, PlanetScale

Initial release

2017

2014

2018

2011

2013

Current release

11.0.0, January 2023

7.x

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

GPL V3

commercial

Open Source

Apache Version 2.0, commercial licenses 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

Prolog, Rust

Server operating systems

Linux

hosted

Linux

Any that supports .NET

Docker
Linux
macOS

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

SQL-like query language (WOQL)

yes

with proprietary extensions

APIs and other access methods

HTTP API

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

.Net

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

JavaScript
Python

.Net

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

similar concept for controling cloud resources

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Journaling Streams

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

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

simple rights management via user accounts

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

Role-based access control

Based on Windows Authentication

Users with fine-grained authorization concept

no user groups or 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.