DBMS > AlaSQL vs. Cubrid vs. Geode vs. Sadas Engine

System Properties Comparison AlaSQL vs. Cubrid vs. Geode vs. Sadas Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Relational DBMS

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

Score	0.49
Rank	#259	Overall
	#40	Document stores
	#120	Relational DBMS

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Website

alasql.org

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

geode.apache.org

www.sadasengine.com

Technical documentation

github.com/AlaSQL/alasql

cubrid.org/manuals

geode.apache.org/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Andrey Gershun & Mathias R. Wulff

CUBRID Corporation, CUBRID Foundation

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

SADAS s.r.l.

Initial release

2014

2008

2002

2006

Current release

11.0, January 2021

1.1, February 2017

8.0

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free trial 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

JavaScript

C, C++, Java

Java

C++

Server operating systems

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

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Linux
Windows

Data scheme

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

SQL-like query language (OQL)

yes

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC
OLE DB

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol

Supported programming languages

JavaScript

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

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

In-memory capabilities

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

yes

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

Access rights for users, groups and roles 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.

Related products and services

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

More resources

Recent citations in the news

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page