DBMS > GridDB vs. RavenDB vs. SAP HANA vs. SpaceTime

System Properties Comparison GridDB vs. RavenDB vs. SAP HANA vs. SpaceTime

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

In-memory, column based data store. Available as appliance or cloud service

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Secondary database models

Key-value store
Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

griddb.net

ravendb.net

www.sap.com/products/hana.html

www.mireo.com/spacetime

Technical documentation

docs.griddb.net

ravendb.net/docs

help.sap.com/hana

Developer

Toshiba Corporation

Hibernating Rhinos

SAP

Mireo

Initial release

2013

2010

2020

Current release

5.1, August 2022

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

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

Open Source

AGPL version 3, commercial license available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (RQL)

yes

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

RESTful HTTP API

Supported programming languages

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

Real-time block device replication (DRBD)

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID, Cluster-wide transaction available

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

Authorization levels configured per client per database

yes

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.