DBMS > Google Cloud Datastore vs. RocksDB vs. RRDtool vs. SAP Advantage Database Server vs. SAP SQL Anywhere

System Properties Comparison Google Cloud Datastore vs. RocksDB vs. RRDtool vs. SAP Advantage Database Server vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

cloud.google.com/datastore

rocksdb.org

oss.oetiker.ch/rrdtool

www.sap.com/products/advantage-database-server.html

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

Technical documentation

cloud.google.com/datastore/docs

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Google

Facebook, Inc.

Tobias Oetiker

Sybase, SAP

SAP

formerly Sybase

Initial release

2008

2013

1999

1993

1992

Current release

8.11.4, April 2024

1.8.0, 2022

17, July 2015

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL V2 and FLOSS

commercial

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

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

hosted

Linux

HP-UX
Linux

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

Numeric data only

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.

Exporting into and restoring from XML files possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

C++ API
Java API

in-process shared library
Pipes

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Delphi
Perl
PHP

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

Server-side scripts

Stored procedures

using Google App Engine

yes

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

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

none

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

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

caching of (temporary) tables can be configured

yes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

More information provided by the system vendor

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.