DBMS > BigObject vs. EsgynDB vs. GridDB vs. OrigoDB

System Properties Comparison BigObject vs. EsgynDB vs. GridDB vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

Technical documentation

docs.bigobject.io

docs.griddb.net

origodb.com/docs

Developer

BigObject, Inc.

Esgyn

Toshiba Corporation

Robert Friberg et al

Initial release

2015

2013

2009

under the name LiveDB

Current release

5.1, August 2022

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

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

Open Source

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

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

.Net

Server-side scripts

Stored procedures

Lua

Java Stored Procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

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

none

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

depending on model

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

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

Write ahead log

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 for users can be defined per database

Role based authorization

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

Toshiba's Distributed Database GridDB(R) Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data ...
3 December 2019, 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

provided by Google News

Share this page