DBMS > Brytlyt vs. Dgraph vs. Newts vs. SQLite vs. TerminusDB

System Properties Comparison Brytlyt vs. Dgraph vs. Newts vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

Distributed and scalable native Graph DBMS

Time Series DBMS based on Cassandra

Widely used embeddable, in-process RDBMS

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

Primary database model

Secondary database models

Document store
RDF store

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

brytlyt.io

dgraph.io

opennms.github.io/newts

www.sqlite.org

terminusdb.com

Technical documentation

docs.brytlyt.io

dgraph.io/docs

github.com/OpenNMS/newts/wiki

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Brytlyt

Dgraph Labs, Inc.

OpenNMS Group

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2016

2014

2000

2018

Current release

5.0, August 2023

3.45.3 (15 April 2024), April 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux
OS X
Windows

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

HTTP REST
Java API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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

Java

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

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

based on Cassandra

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication via Raft

selectable replication factor

based on Cassandra

none

Journaling Streams

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

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 journaling

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

Planned for future releases

Role-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.