DBMS > Brytlyt vs. Ehcache vs. HEAVY.AI vs. Lovefield vs. RocksDB

System Properties Comparison Brytlyt vs. Ehcache vs. HEAVY.AI vs. Lovefield vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted Java cache with tiered storage options

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

Embeddable relational database for web apps written in pure JavaScript

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

Primary database model

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	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

brytlyt.io

www.ehcache.org

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

google.github.io/lovefield

rocksdb.org

Technical documentation

docs.brytlyt.io

www.ehcache.org/documentation

docs.heavy.ai

github.com/google/lovefield/blob/master/docs/spec_index.md

github.com/facebook/rocksdb/wiki

Developer

Brytlyt

Terracotta Inc, owned by Software AG

HEAVY.AI, Inc.

Google

Facebook, Inc.

Initial release

2016

2009

2016

2014

2013

Current release

5.0, August 2023

3.10.0, March 2022

5.10, January 2022

2.1.12, February 2017

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

BSD

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

C++ and CUDA

JavaScript

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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-like query language

via JavaScript builder pattern

APIs and other access methods

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

JCache

JDBC
ODBC
Thrift
Vega

C++ API
Java API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Java

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Triggers

yes

Cache Event Listeners

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Round robin

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

by using Terracotta Server

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

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.