DBMS > Brytlyt vs. GeoMesa vs. H2 vs. OrigoDB vs. TerarkDB

System Properties Comparison Brytlyt vs. GeoMesa vs. H2 vs. OrigoDB vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

A fully ACID in-memory object graph database

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Document store
Object oriented DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

github.com/bytedance/terarkdb

Technical documentation

docs.brytlyt.io

www.geomesa.org/documentation/stable/user/index.html

www.h2database.com/html/main.html

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Brytlyt

CCRi and others

Thomas Mueller

Robert Friberg et al

ByteDance, originally Terark

Initial release

2016

2014

2005

2009

under the name LiveDB

2016

Current release

5.0, August 2023

4.0.5, February 2024

2.2.220, July 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

commercial

restricted open source version available

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

Scala

Java

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

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

JDBC
ODBC

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Java

.Net

C++
Java

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Java Stored Procedures and User-Defined Functions

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

With clustering: 2 database servers on different computers operate on identical copies of a database

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Brytlyt releases version 5.0, introducing a more intuitive, intelligent and flexible analytics platform
1 August 2023, PR Newswire

London data analytics startup Brytlyt raises €4.43M from Amsterdam-based Finch Capital, others
22 December 2021, Silicon Canals

Brytlyt Secures $4M in Series A Funding
20 May 2020, Datanami

Brytlyt becomes NVIDIA Inception Premier Partner
31 January 2023, PR Newswire

London’s Brytlyt raises €4.4 million for its data analytics and visualisation technology
22 December 2021, EU-Startups

provided by Google News

A Chinese company is making the cloud 200x faster · TechNode
3 July 2017, TechNode

provided by Google News

Share this page