DBMS > Google Cloud Datastore vs. Interbase vs. IRONdb vs. NSDb vs. RocksDB

System Properties Comparison Google Cloud Datastore vs. Interbase vs. IRONdb vs. NSDb vs. RocksDB

Editorial information provided by DB-Engines

Name

IRONdb 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

Light-weight proven RDBMS

originally from Borland

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

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	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Website

cloud.google.com/datastore

www.embarcadero.com/products/interbase

www.circonus.com/solutions/time-series-database/

nsdb.io

rocksdb.org

Technical documentation

cloud.google.com/datastore/docs

docs.embarcadero.com/products/interbase

docs.circonus.com/irondb/category/getting-started

nsdb.io/Architecture

github.com/facebook/rocksdb/wiki

Developer

Google

Embarcadero

Circonus LLC.

Facebook, Inc.

Initial release

2008

1984

2017

2013

Current release

InterBase 2020, December 2019

V0.10.20, January 2018

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

BSD

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

Java, Scala

C++

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

Linux

Linux
macOS

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

text, numeric, histograms

yes: int, bigint, decimal, string

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.

export as XML data possible

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

APIs and other access methods

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

ADO.NET
JDBC
ODBC

HTTP API

gRPC
HTTP REST
WebSocket

C++ API
Java API

Supported programming languages

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

yes

Interbase procedure and trigger language

yes, in Lua

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Interbase Change Views

configurable replication factor, datacenter aware

yes

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.

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual 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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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, 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.