DBMS > Derby vs. Google BigQuery vs. SpatiaLite vs. SwayDB

System Properties Comparison Derby vs. Google BigQuery vs. SpatiaLite vs. SwayDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Large scale data warehouse service with append-only tables

Spatial extension of SQLite

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Spatial DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

db.apache.org/derby

cloud.google.com/bigquery

www.gaia-gis.it/fossil/libspatialite/index

swaydb.simer.au

Technical documentation

db.apache.org/derby/manuals/index.html

cloud.google.com/bigquery/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Apache Software Foundation

Google

Alessandro Furieri

Simer Plaha

Initial release

1997

2010

2008

2018

Current release

10.17.1.0, November 2023

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

GNU Affero GPL V3.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

Java

C++

Scala

Server operating systems

All OS with a Java VM

hosted

server-less

Data scheme

yes

schema-free

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

APIs and other access methods

JDBC

RESTful HTTP/JSON API

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Atomic execution of operations

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

fine grained access rights according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

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.