DBMS > Quasardb vs. Snowflake vs. Splunk vs. TerminusDB vs. Yaacomo

System Properties Comparison Quasardb vs. Snowflake vs. Splunk vs. TerminusDB vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Distributed, high-performance timeseries database

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

Analytics Platform for Big Data

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Secondary database models

Document store
RDF store

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

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

yaacomo.com

Technical documentation

doc.quasar.ai/master

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

terminusdb.github.io/terminusdb/#

Developer

quasardb

Snowflake Computing Inc.

Splunk Inc.

DataChemist Ltd.

Q2WEB GmbH

Initial release

2009

2014

2003

2018

2009

Current release

3.14.1, January 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Limited free edition and free developer edition available

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

Prolog, Rust

Server operating systems

BSD
Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Linux

Android
Linux
Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

Splunk Search Processing Language for search commands

SQL-like query language (WOQL)

yes

APIs and other access methods

HTTP API

CLI Client
JDBC
ODBC

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

yes

Sharding

Graph Partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with selectable replication factor

yes

Multi-source replication

Journaling Streams

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

by using LevelDB

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

Transient mode

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

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

Access rights for users and roles

Role-based access control

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.