DBMS > Google Cloud Datastore vs. Infobright vs. JanusGraph vs. Oracle

System Properties Comparison Google Cloud Datastore vs. Infobright vs. JanusGraph vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

cloud.google.com/datastore

ignitetech.com/softwarelibrary/infobrightdb

janusgraph.org

www.oracle.com/database

Technical documentation

cloud.google.com/datastore/docs

docs.janusgraph.org

docs.oracle.com/en/database

Developer

Google

Ignite Technologies Inc.; formerly InfoBright Inc.

Linux Foundation; originally developed as Titan by Aurelius

Oracle

Initial release

2008

2005

2017

1980

Current release

0.6.3, February 2023

23c, September 2023

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache 2.0

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

Java

C and C++

Server operating systems

hosted

Linux
Windows

Linux
OS X
Unix
Windows

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

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes, details here

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

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

ADO.NET
JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java
Python

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

using Google App Engine

yes

PL/SQL

also stored procedures in Java possible

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via Faunus, a graph analytics engine

can be realized in PL/SQL

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

User authentification and security via Rexster Graph Server

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.