DBMS > Apache Impala vs. Google Cloud Datastore vs. IBM Cloudant vs. Oracle vs. TigerGraph

System Properties Comparison Apache Impala vs. Google Cloud Datastore vs. IBM Cloudant vs. Oracle vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Database as a Service offering based on Apache CouchDB

Widely used RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Document store

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	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

impala.apache.org

cloud.google.com/datastore

www.ibm.com/products/cloudant

www.oracle.com/database

www.tigergraph.com

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/datastore/docs

cloud.ibm.com/docs/Cloudant

docs.oracle.com/en/database

docs.tigergraph.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

Initial release

2013

2008

2010

1980

2017

Current release

4.1.0, June 2022

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

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

Erlang

C and C++

C++

Server operating systems

Linux

hosted

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

Linux

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (GQL)

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

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

RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

using Google App Engine

View functions (Map-Reduce) in JavaScript

PL/SQL

also stored procedures in Java possible

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

using Google Cloud Dataflow

yes

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

atomic operations within a document possible

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Role-based access control

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.