DBMS > Google Cloud Datastore vs. Kdb vs. Oracle vs. SAP SQL Anywhere

System Properties Comparison Google Cloud Datastore vs. Kdb vs. Oracle vs. SAP SQL Anywhere

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 performance Time Series DBMS

Widely used RDBMS

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

Primary database model

Document store

Time Series DBMS
Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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	7.55
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

cloud.google.com/datastore

kx.com

www.oracle.com/database

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

Technical documentation

cloud.google.com/datastore/docs

code.kx.com

docs.oracle.com/en/database

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Google

Kx Systems, a division of First Derivatives plc

Oracle

SAP

formerly Sybase

Initial release

2008

2000

kdb was released 2000, kdb+ in 2003

1980

1992

Current release

3.6, May 2018

23c, September 2023

17, July 2015

License

Commercial or Open Source

commercial

free 32-bit version

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

Server operating systems

hosted

Linux
OS X
Solaris
Windows

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

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

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

table attribute 'grouped'

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language (q)

yes

with proprietary extensions

yes

APIs and other access methods

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

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
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

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

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

PL/SQL

also stored procedures in Java possible

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

Triggers

Callbacks using the Google Apps Engine

yes

with views

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

similar paradigm used for internal processing

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

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

ACID

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'

yes

User concepts

Access control

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

rights management via user accounts

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» more

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.