DBMS > Google BigQuery vs. LokiJS vs. Microsoft Access vs. Solr vs. STSdb

System Properties Comparison Google BigQuery vs. LokiJS vs. Microsoft Access vs. Solr vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

In-memory JavaScript DBMS

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

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	0.43
Rank	#264	Overall
	#42	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

cloud.google.com/bigquery

github.com/techfort/LokiJS

www.microsoft.com/en-us/microsoft-365/access

solr.apache.org

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/bigquery/docs

techfort.github.io/LokiJS

developer.microsoft.com/en-us/access

solr.apache.org/resources.html

Developer

Google

Microsoft

Apache Software Foundation

STS Soft SC

Initial release

2010

2014

1992

2006

2011

Current release

1902 (16.0.11328.20222), March 2019

9.6.0, April 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2

Open Source

GPLv2, commercial license available

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

Server operating systems

hosted

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

Windows

Not a real database server, but making use of DLLs

All OS with a Java VM

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

Windows

Data scheme

yes

schema-free

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

primitive types and user defined types (classes)

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

via views

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

but not compliant to any SQL standard

Solr Parallel SQL Interface

APIs and other access methods

RESTful HTTP/JSON API

JavaScript API

ADO.NET
DAO
ODBC
OLE DB

Java API
RESTful HTTP/JSON API

.NET Client API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

Java plugins

Triggers

yes

since Access 2010 using the ACE-engine

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

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

atomic operations within a single collection possible

ACID

but no files for transaction logging

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

but no files for transaction logging

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)

a simple user-level security was built in till version Access 2003

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.