DBMS > GBase vs. Google Cloud Datastore vs. IRONdb vs. Oracle

System Properties Comparison GBase vs. Google Cloud Datastore vs. IRONdb vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

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

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

Widely used RDBMS

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

www.gbase.cn

cloud.google.com/datastore

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

www.oracle.com/database

Technical documentation

cloud.google.com/datastore/docs

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

docs.oracle.com/en/database

Developer

General Data Technology Co., Ltd.

Google

Circonus LLC.

Oracle

Initial release

2004

2008

2017

1980

Current release

GBase 8a, GBase 8s, GBase 8c

V0.10.20, January 2018

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is 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, Java, Python

C and C++

Server operating systems

Linux

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes

yes, details here

yes

text, numeric, histograms

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

SQL-like query language (GQL)

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

yes

with proprietary extensions

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

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

HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

yes, in Lua

PL/SQL

also stored procedures in Java possible

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

Automatic, metric affinity per node

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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 per node, eventual consistency across nodes

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

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

yes

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.