DBMS > Google BigQuery vs. LevelDB vs. PostGIS vs. RavenDB vs. RDF4J

System Properties Comparison Google BigQuery vs. LevelDB vs. PostGIS vs. RavenDB vs. RDF4J

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Spatial extension of PostgreSQL

Open Source Operational and Transactional Enterprise NoSQL Document Database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Secondary database models

Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Website

cloud.google.com/bigquery

github.com/google/leveldb

postgis.net

ravendb.net

rdf4j.org

Technical documentation

cloud.google.com/bigquery/docs

github.com/google/leveldb/blob/main/doc/index.md

postgis.net/documentation

ravendb.net/docs

rdf4j.org/documentation

Developer

Google

Hibernating Rhinos

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2010

2011

2005

2010

2004

Current release

1.23, February 2021

3.4.2, February 2024

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL v2.0

Open Source

AGPL version 3, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Java

Server operating systems

hosted

Illumos
Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

RDF Schemas

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

yes

SQL-like query language (RQL)

APIs and other access methods

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

ACID, Cluster-wide transaction available

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

in-memory storage is supported as well

In-memory capabilities

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

based on PostgreSQL

Authorization levels configured per client per database

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.