DBMS > Google Cloud Datastore vs. Virtuoso vs. XTDB

System Properties Comparison Google Cloud Datastore vs. Virtuoso vs. XTDB

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

Virtuoso is a multi-model hybrid-RDBMS that supports management of data represented as relational tables and/or property graphs

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

Document store
Graph DBMS
Native XML DBMS
Relational DBMS
RDF store
Search engine

Document store

Secondary database models

Spatial DBMS

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

Score	3.62
Rank	#71	Overall
	#12	Document stores

Score	2.79
Rank	#89	Overall
	#15	Document stores
	#5	Graph DBMS
	#2	Native XML DBMS
	#48	Relational DBMS
	#2	RDF stores
	#10	Search engines

Score	0.20
Rank	#314	Overall
	#46	Document stores

Website

cloud.google.com/datastore

virtuoso.openlinksw.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

cloud.google.com/datastore/docs

docs.openlinksw.com/virtuoso

www.xtdb.com/docs

Developer

Google

OpenLink Software

Juxt Ltd.

Initial release

2008

1998

2019

Current release

7.2.11, September 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

MIT License

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

Clojure

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

SQL - Standard relational schema
RDF - Quad (S, P, O, G) or Triple (S, P, O)
XML - DTD, XML Schema
DAV - freeform filesystem objects, plus User Defined Types a/k/a Dynamic Extension Type

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

yes, extensible-data-notation format

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, SQL-200x, SQL-3, SQLX

limited SQL, making use of Apache Calcite

APIs and other access methods

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

ADO.NET
GeoSPARQL
HTTP API
JDBC
Jena RDF API
ODBC
OLE DB
RDF4J API
RESTful HTTP API
Sesame REST HTTP Protocol
SOAP webservices
SPARQL 1.1
WebDAV
XPath
XQuery
XSLT

HTTP REST
JDBC

Supported programming languages

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

.Net
C
C#
C++
Java
JavaScript
Perl
PHP
Python
Ruby
Visual Basic

Clojure
Java

Server-side scripts

Stored procedures

using Google App Engine

yes

Virtuoso PL

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Chain, star, and bi-directional replication
Multi-source replication
Source-replica replication

yes, each node contains all data

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.

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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)

Fine-grained Attribute-Based Access Control (ABAC) in addition to typical coarse-grained Role-Based Access Control (RBAC) according to SQL-standard. Pluggable authentication with supported standards (LDAP, Active Directory, Kerberos)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Best cloud storage of 2025: tested, reviewed and rated by experts
9 May 2025, TechRadar

Storage news ticker – April 11
11 April 2025, Blocks and Files

Best Cloud Storage Options for All Your Data in 2025
16 April 2025, CNET

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
5 April 2025, Cloudwards.net

Enabling Security for Hadoop Data Lake on Google Cloud Storage
30 July 2024, Uber

provided by Google News

Figure 2. DAR detailed architecture
11 March 2018, ResearchGate

Fig. 1. Logical architecture of the OPENNESS platform.
7 February 2018, ResearchGate

provided by Google News

Share this page