DBMS > Google Cloud Datastore vs. Kinetica vs. SQLite vs. TimesTen vs. Transwarp StellarDB

System Properties Comparison Google Cloud Datastore vs. Kinetica vs. SQLite vs. TimesTen vs. Transwarp StellarDB

Editorial information provided by DB-Engines

Name

Description

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

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

In-Memory RDBMS compatible to Oracle

A distributed graph DBMS built for enterprise-level graph applications

Primary database model

Document store

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Score	0.07
Rank	#371	Overall
	#39	Graph DBMS

Website

cloud.google.com/datastore

www.kinetica.com

www.sqlite.org

www.oracle.com/database/technologies/related/timesten.html

www.transwarp.cn/en/product/stellardb

Technical documentation

cloud.google.com/datastore/docs

docs.kinetica.com

www.sqlite.org/docs.html

docs.oracle.com/database/timesten-18.1

Developer

Google

Kinetica

Dwayne Richard Hipp

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Transwarp

Initial release

2008

2012

2000

1998

Current release

7.1, August 2021

3.46.0 (23 May 2024), May 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

Public Domain

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

Server operating systems

hosted

Linux

server-less

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

yes

SQL-like query language

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

OpenCypher

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

PL/SQL

Triggers

Callbacks using the Google Apps Engine

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

none

Multi-source replication
Source-replica replication

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 or Eventual Consistency depending on configuration

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

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

yes

User concepts

Access control

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

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

yes

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.