DBMS > AgensGraph vs. Amazon Redshift vs. BigObject vs. GridDB

System Properties Comparison AgensGraph vs. Amazon Redshift vs. BigObject vs. GridDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

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

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

a hierachical model (tree) can be imposed

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.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

bigobject.io

griddb.net

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

docs.griddb.net

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

BigObject, Inc.

Toshiba Corporation

Initial release

2016

2012

2015

2013

Current release

2.1, December 2018

5.1, August 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free community edition available

Open Source

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

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

Data scheme

depending on used data model

yes

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

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

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Source-replica replication

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

none

Immediate consistency within container, eventual consistency across containers

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

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 lock on objects (tables, trees)

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

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.