DBMS > BigchainDB vs. GeoSpock vs. Google BigQuery vs. SAP Advantage Database Server vs. Solr

System Properties Comparison BigchainDB vs. GeoSpock vs. Google BigQuery vs. SAP Advantage Database Server vs. Solr

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

Document store

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.bigchaindb.com

geospock.com

cloud.google.com/bigquery

www.sap.com/products/advantage-database-server.html

solr.apache.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/bigquery/docs

solr.apache.org/resources.html

Developer

GeoSpock

Google

Sybase, SAP

Apache Software Foundation

Initial release

2016

2010

1993

2006

Current release

2.0, September 2019

9.6.0, April 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

Apache Version 2

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

Python

Java, Javascript

Java

Server operating systems

Linux

hosted

Linux
Windows

All OS with a Java VM

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

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

temporal, categorical

yes

All search fields are automatically indexed

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

Solr Parallel SQL Interface

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Delphi
Perl
PHP

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

caching of (temporary) tables can be configured

yes

User concepts

Access control

yes

Access rights for users can be defined per table

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

yes

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.