DBMS > Brytlyt vs. Cubrid vs. Geode vs. mSQL vs. SAP HANA

System Properties Comparison Brytlyt vs. Cubrid vs. Geode vs. mSQL vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

mSQL (Mini SQL) is a simple and lightweight RDBMS

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

brytlyt.io

cubrid.com (korean)
cubrid.org (english)

geode.apache.org

hughestech.com.au/products/msql

www.sap.com/products/hana.html

Technical documentation

docs.brytlyt.io

cubrid.org/manuals

geode.apache.org/docs

help.sap.com/hana

Developer

Brytlyt

CUBRID Corporation, CUBRID Foundation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Hughes Technologies

SAP

Initial release

2016

2008

2002

1994

2010

Current release

5.0, August 2023

11.0, January 2021

1.1, February 2017

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free licenses can be provided

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based 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++, Java

Java

Server operating systems

Linux
OS X
Windows

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

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 (OQL)

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
OLE DB

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Java Stored Procedures

user defined functions

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

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

Access rights per client and object definable

yes

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.