DBMS > Google Cloud Datastore vs. Microsoft Azure Table Storage vs. SAP SQL Anywhere vs. SQLite vs. TerminusDB

System Properties Comparison Google Cloud Datastore vs. Microsoft Azure Table Storage vs. SAP SQL Anywhere vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

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

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

cloud.google.com/datastore

azure.microsoft.com/en-us/services/storage/tables

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

www.sqlite.org

terminusdb.com

Technical documentation

cloud.google.com/datastore/docs

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Google

Microsoft

SAP

formerly Sybase

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2008

2012

1992

2000

2018

Current release

17, July 2015

3.46.0 (23 May 2024), May 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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 query language (GQL)

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

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

RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

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

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

using Google App Engine

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

yes

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

Database mirroring

none

Journaling Streams

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

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory journaling

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)

Access rights based on private key authentication or shared access signatures

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.