DBMS > Google BigQuery vs. Oracle NoSQL vs. Sadas Engine vs. Solr

System Properties Comparison Google BigQuery vs. Oracle NoSQL vs. Sadas Engine vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

cloud.google.com/bigquery

www.oracle.com/database/nosql/technologies/nosql

www.sadasengine.com

solr.apache.org

Technical documentation

cloud.google.com/bigquery/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

solr.apache.org/resources.html

Developer

Google

Oracle

SADAS s.r.l.

Apache Software Foundation

Initial release

2010

2011

2006

Current release

23.3, December 2023

8.0

9.6.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

free trial version available

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

Java

C++

Java

Server operating systems

hosted

Linux
Solaris SPARC/x86

AIX
Linux
Windows

All OS with a Java VM

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

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

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

Typing

predefined data types such as float or date

yes

optional

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

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

Solr Parallel SQL Interface

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

JDBC
ODBC
Proprietary protocol

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
Go
Java
JavaScript (Node.js)
Python

.Net
C
C#
C++
Groovy
Java
PHP
Python

.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

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

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

depending on configuration

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

configurable

ACID within a storage node (=shard)

optimistic locking

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

off heap cache

yes

managed by 'Learn by Usage'

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

Access rights for users, groups and roles 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.