DBMS > Geode vs. Google BigQuery vs. Virtuoso

System Properties Comparison Geode vs. Google BigQuery vs. Virtuoso

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Large scale data warehouse service with append-only tables

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

Primary database model

Key-value store

Relational DBMS

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

Secondary database models

Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.26
Rank	#78	Overall
	#13	Document stores
	#4	Graph DBMS
	#2	Native XML DBMS
	#42	Relational DBMS
	#2	RDF stores
	#9	Search engines

Website

geode.apache.org

cloud.google.com/bigquery

virtuoso.openlinksw.com

Technical documentation

geode.apache.org/docs

cloud.google.com/bigquery/docs

docs.openlinksw.com/virtuoso

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

OpenLink Software

Initial release

2002

2010

1998

Current release

1.1, February 2017

7.2.11, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPLv2, extended commercial license available

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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
Solaris
Windows

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

Typing

predefined data types such as float or date

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 (OQL)

yes

SQL-92, SQL-200x, SQL-3, SQLX

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP 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

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Virtuoso PL

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

Since BigQuery is designed for querying data

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

User concepts

Access control

Access rights per client and object definable

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & 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

Specific characteristics

Virtuoso is a modern multi-model RDBMS for managing data represented as tabular relations...
» more

Competitive advantages

Performance & Scale — as exemplified by DBpedia and the LOD Cloud it spawned, i.e.,...
» more

Typical application scenarios

Used for — Analytics/BI Conceptual Data Virtualization Enterprise Knowledge Graphs...
» more

Key customers

Broad use across enterprises and governments including — European Union (EU) US Government...
» more

Market metrics

Largest installed-base of Multi-Model RDBMS for AI-friendly Knowledge Graphs Platform...
» more

Licensing and pricing models

Available in both Commercial Enterprise and Open Source (GPL v2) Editions Feature...
» 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.