DBMS > Brytlyt vs. Newts vs. Riak KV vs. SQLite

System Properties Comparison Brytlyt vs. Newts vs. Riak KV vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS based on Cassandra

Distributed, fault tolerant key-value store

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	0.38
Rank	#279	Overall
	#126	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

brytlyt.io

opennms.github.io/newts

www.sqlite.org

Technical documentation

docs.brytlyt.io

github.com/OpenNMS/newts/wiki

www.tiot.jp/riak-docs/riak/kv/latest

www.sqlite.org/docs.html

Developer

Brytlyt

OpenNMS Group

OpenSource, formerly Basho Technologies

Dwayne Richard Hipp

Initial release

2016

2014

2009

2000

Current release

5.0, August 2023

3.2.0, December 2022

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++ and CUDA

Java

Erlang

Server operating systems

Linux
OS X
Windows

Linux
OS X

server-less

Data scheme

yes

schema-free

yes

dynamic column types

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

restricted

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

HTTP REST
Java API

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

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

yes, using Riak Security

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.