DBMS > Brytlyt vs. Graph Engine vs. InfinityDB vs. RocksDB vs. SQream DB

System Properties Comparison Brytlyt vs. Graph Engine vs. InfinityDB vs. RocksDB vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A Java embedded Key-Value Store which extends the Java Map interface

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Key-value store

Relational DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

Technical documentation

docs.brytlyt.io

www.graphengine.io/docs/manual

boilerbay.com/infinitydb/manual

github.com/facebook/rocksdb/wiki

docs.sqream.com

Developer

Brytlyt

Microsoft

Boiler Bay Inc.

Facebook, Inc.

SQream Technologies

Initial release

2016

2010

2002

2013

2017

Current release

5.0, August 2023

4.0

9.2.1, May 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

BSD

commercial

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

.NET and C

Java

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
OS X
Windows

.NET

All OS with a Java VM

Linux

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

schema-free

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes, ANSI Standard SQL Types

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

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

yes

APIs and other access methods

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

RESTful HTTP API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

C++ API
Java API

.Net
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C#
C++
F#
Visual Basic

Java

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

horizontal partitioning

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Optimistic locking for transactions; no isolation for bulk loads

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.