DBMS > IBM Db2 Event Store vs. Sequoiadb vs. Snowflake vs. Tkrzw vs. Yaacomo

System Properties Comparison IBM Db2 Event Store vs. Sequoiadb vs. Snowflake vs. Tkrzw vs. Yaacomo

Editorial information provided by DB-Engines

Name

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

Description

Distributed Event Store optimized for Internet of Things use cases

NewSQL database with distributed OLTP and SQL

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

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

Primary database model

Event Store
Time Series DBMS

Document store
Relational DBMS

Relational DBMS

Key-value store

Relational DBMS

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

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.ibm.com/products/db2-event-store

www.sequoiadb.com

www.snowflake.com

dbmx.net/tkrzw

yaacomo.com

Technical documentation

www.ibm.com/docs/en/db2-event-store

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

Developer

IBM

Sequoiadb Ltd.

Snowflake Computing Inc.

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2017

2013

2014

2020

2009

Current release

2.0

0.9.3, August 2020

License

Commercial or Open Source

commercial

free developer edition available

Open Source

Server: AGPL; Client: Apache V2

commercial

Open Source

Apache Version 2.0

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

C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux

hosted

Linux
macOS

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

through the embedded Spark runtime

SQL-like query language

yes

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

proprietary protocol using JSON

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

JavaScript

user defined functions

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

Source-replica 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

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

No - written data is immutable

yes

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

yes

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

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.