DBMS > AlaSQL vs. Google BigQuery vs. Oracle Berkeley DB vs. Solr vs. XTDB

System Properties Comparison AlaSQL vs. Google BigQuery vs. Oracle Berkeley DB vs. Solr vs. XTDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service with append-only tables

Widely used in-process key-value store

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Search engine

Document store

Secondary database models

Spatial DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

alasql.org

cloud.google.com/bigquery

www.oracle.com/database/technologies/related/berkeleydb.html

solr.apache.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

docs.oracle.com/cd/E17076_05/html/index.html

solr.apache.org/resources.html

www.xtdb.com/docs

Developer

Andrey Gershun & Mathias R. Wulff

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation

Juxt Ltd.

Initial release

2014

2010

1994

2006

2019

Current release

18.1.40, May 2020

9.6.0, April 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

commercial license available

Open Source

Apache Version 2

Open Source

MIT 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

JavaScript

C, Java, C++ (depending on the Berkeley DB edition)

Java

Clojure

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java VM

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

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes, extensible-data-notation format

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

SQL interfaced based on SQLite is available

Solr Parallel SQL Interface

limited SQL, making use of Apache Calcite

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java plugins

Triggers

yes

only for the SQL API

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

yes, each node contains all data

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

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

Since BigQuery is designed for querying data

ACID

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.