DBMS > Google BigQuery vs. RDF4J vs. Solr vs. Spark SQL vs. Transbase

System Properties Comparison Google BigQuery vs. RDF4J vs. Solr vs. Spark SQL vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

A widely used distributed, scalable search engine based on Apache Lucene

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

cloud.google.com/bigquery

rdf4j.org

solr.apache.org

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

Technical documentation

cloud.google.com/bigquery/docs

rdf4j.org/documentation

solr.apache.org/resources.html

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

Google

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

Apache Software Foundation

Transaction Software GmbH

Initial release

2010

2004

2006

2014

1987

Current release

9.6.1, May 2024

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

free development 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

Java

Scala

C and C++

Server operating systems

hosted

Linux
OS X
Unix
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

RDF Schemas

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

Solr Parallel SQL Interface

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP/JSON API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Java API
RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
PHP
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Java plugins

yes

Triggers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

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

Isolation support depends on the API used

optimistic locking

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

fine grained access rights according to SQL-standard

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.