DBMS > Brytlyt vs. HEAVY.AI vs. KairosDB vs. SQLite vs. Yanza

System Properties Comparison Brytlyt vs. HEAVY.AI vs. KairosDB vs. SQLite vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Distributed Time Series DBMS based on Cassandra or H2

Widely used embeddable, in-process RDBMS

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

brytlyt.io

github.com/heavyai/heavydb
www.heavy.ai

github.com/kairosdb/kairosdb

www.sqlite.org

yanza.com

Technical documentation

docs.brytlyt.io

docs.heavy.ai

kairosdb.github.io

www.sqlite.org/docs.html

Developer

Brytlyt

HEAVY.AI, Inc.

Dwayne Richard Hipp

Yanza

Initial release

2016

2013

2000

2015

Current release

5.0, August 2023

5.10, January 2022

1.2.2, November 2018

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++ and CUDA

C++ and CUDA

Java

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Windows

server-less

Windows

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
Thrift
Vega

Graphite protocol
HTTP REST
Telnet API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

All languages supporting JDBC/ODBC/Thrift
Python

Java
JavaScript

Node.js
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

via file-system locks

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

fine grained access rights according to SQL-standard

simple password-based access control

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.