DBMS > GridDB vs. OrigoDB vs. Realm vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison GridDB vs. OrigoDB vs. Realm vs. RocksDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

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

A fully ACID in-memory object graph database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Time Series DBMS

Document store
Object oriented DBMS

Document store

Key-value store

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

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

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.griddb.net

origodb.com/docs

realm.io/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Toshiba Corporation

Robert Friberg et al

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

SAP

formerly Sybase

Initial release

2013

2009

under the name LiveDB

2014

2013

1992

Current release

5.1, August 2022

8.11.4, April 2024

17, July 2015

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

BSD

commercial

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++

Server operating systems

Linux

Linux
Windows

Android
Backend: server-less
iOS
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

.Net

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Domain Events

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

Source-replica replication

Database mirroring

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 within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID at container level

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

yes

User concepts

Access control

Access rights for users can be defined per database

Role based authorization

yes

fine grained access rights according to SQL-standard

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.