DBMS > ArcadeDB vs. GridDB vs. LeanXcale vs. OpenQM

System Properties Comparison ArcadeDB vs. GridDB vs. LeanXcale vs. OpenQM

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Time Series DBMS

Key-value store
Relational DBMS

Multivalue DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	0.02
Rank	#366	Overall
	#50	Document stores
	#38	Graph DBMS
	#53	Key-value stores
	#36	Time Series DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

arcadedb.com

griddb.net

www.leanxcale.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

docs.arcadedb.com

docs.griddb.net

Developer

Arcade Data

Toshiba Corporation

LeanXcale

Rocket Software, originally Martin Phillips

Initial release

2021

2013

2015

1993

Current release

September 2021

5.1, August 2022

3.4-12

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

GPLv2, extended commercial license 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

Java

C++

Server operating systems

All OS with a Java VM

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

schema-free

yes

with some exceptions

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

SQL92, SQL-like TQL (Toshiba Query Language)

yes

through Apache Derby

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

Supported programming languages

Java

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

C
Java
Scala

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

ACID at container level

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

Access rights for users can be defined per database

Access rights can be defined down to the item level

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.

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

General Availability of GridDB® 5.5 Enterprise Edition ~Enhancing the efficiency of IoT system development and ...
16 January 2024, global.toshiba

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

GridDB Use case Large-scale high-speed processing of smart meter data following the deregulation of electrical power ...
1 November 2020, global.toshiba

General Availability of GridDB 5.1 Enterprise Edition ~ Continuous database usage in the event of data center failure ...
19 August 2022, global.toshiba

IoT: Opt for the Right Open Source Database
11 August 2023, Open Source For You

provided by Google News

Share this page