DBMS > Brytlyt vs. Couchbase vs. GeoMesa vs. GridDB

System Properties Comparison Brytlyt vs. Couchbase vs. GeoMesa vs. GridDB

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

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

Scalable in-memory time series database optimized for IoT and Big Data

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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	16.59
Rank	#36	Overall
	#5	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Website

Technical documentation

docs.brytlyt.io

docs.couchbase.com

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

docs.griddb.net

Developer

Brytlyt

Couchbase, Inc.

CCRi and others

Toshiba Corporation

Initial release

2016

2011

2014

2013

Current release

5.0, August 2023

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

5.0.0, May 2024

5.1, August 2022

License

Commercial or Open Source

commercial

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache License 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also 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

C, C++, Go and Erlang

Scala

C++

Server operating systems

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

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

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

including cross data center replication
Source-replica replication

depending on storage layer

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

depending on storage layer

Immediate consistency within container, eventual consistency across containers

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID at container level

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

Ephemeral buckets

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

yes

depending on the DBMS used for storage

Access rights for users can be defined per database

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.