DBMS > EJDB vs. GBase vs. GridDB vs. Machbase Neo

System Properties Comparison EJDB vs. GBase vs. GridDB vs. Machbase Neo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

TimeSeries DBMS for AIoT and BigData

Primary database model

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Website

github.com/Softmotions/ejdb

www.gbase.cn

griddb.net

machbase.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.griddb.net

machbase.com/dbms

Developer

Softmotions

General Data Technology Co., Ltd.

Toshiba Corporation

Machbase

Initial release

2012

2004

2013

Current release

GBase 8a, GBase 8s, GBase 8c

5.1, August 2022

V8.0, August 2023

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

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

commercial

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

C, Java, Python

C++

Server operating systems

server-less

Linux

Linux
macOS
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

numerical, string, blob, geometry, boolean, timestamp

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

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

APIs and other access methods

in-process shared library

ADO.NET
C API
JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

selectable replication factor

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

volatile and lookup table

User concepts

Access control

yes

Access rights for users can be defined per database

simple password-based access control

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

General Availability of GridDB 5.3 Enterprise Edition ~ Major Enhancement in IoT and Time Series Data Analysis ...
16 May 2023, global.toshiba

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

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

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

provided by Google News

Share this page