DBMS > Brytlyt vs. GigaSpaces vs. Google BigQuery vs. LMDB

System Properties Comparison Brytlyt vs. GigaSpaces vs. Google BigQuery vs. LMDB

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Large scale data warehouse service with append-only tables

A high performant, light-weight, embedded key-value database library

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Key-value store

Secondary database models

Graph DBMS
Search engine

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Website

brytlyt.io

www.gigaspaces.com

cloud.google.com/bigquery

www.symas.com/symas-embedded-database-lmdb

Technical documentation

docs.brytlyt.io

docs.gigaspaces.com/latest/landing.html

cloud.google.com/bigquery/docs

www.lmdb.tech/doc

Developer

Brytlyt

Gigaspaces Technologies

Google

Symas

Initial release

2016

2000

2010

2011

Current release

5.0, August 2023

15.5, September 2020

0.9.32, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

commercial

Open Source

Cloud-based only

Only available as a cloud service

yes

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++, .Net

Server operating systems

Linux
OS X
Windows

Linux
macOS
Solaris
Windows

hosted

Linux
Unix
Windows

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-99 for query and DML statements

yes

APIs and other access methods

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

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C++
Java
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

user defined functions

in JavaScript

Triggers

yes

yes, event driven architecture

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.