DBMS > Google Cloud Datastore vs. RavenDB vs. SQLite vs. VoltDB

System Properties Comparison Google Cloud Datastore vs. RavenDB vs. SQLite vs. VoltDB

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Widely used embeddable, in-process RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

cloud.google.com/datastore

ravendb.net

www.sqlite.org

www.voltdb.com

Technical documentation

cloud.google.com/datastore/docs

ravendb.net/docs

www.sqlite.org/docs.html

docs.voltdb.com

Developer

Google

Hibernating Rhinos

Dwayne Richard Hipp

VoltDB Inc.

Initial release

2008

2010

2000

2010

Current release

5.4, July 2022

3.45.3 (15 April 2024), April 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Public Domain

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

server-less

Linux
OS X

for development

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

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

Java

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

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.

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID, Cluster-wide transaction available

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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)

Authorization levels configured per client per database

Users and roles with access to stored procedures

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.