DBMS > Elasticsearch vs. Google BigQuery vs. Linter vs. Microsoft Access vs. SiriDB

System Properties Comparison Elasticsearch vs. Google BigQuery vs. Linter vs. Microsoft Access vs. SiriDB

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Large scale data warehouse service with append-only tables

RDBMS for high security requirements

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.)

Open Source Time Series DBMS

Primary database model

Search engine

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Spatial DBMS

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Website

www.elastic.co/elasticsearch

cloud.google.com/bigquery

linter.ru

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

siridb.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

docs.siridb.com

Developer

Elastic

Google

relex.ru

Microsoft

Cesbit

Initial release

2010

1990

1992

2017

Current release

8.6, January 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Elastic License

commercial

Bundled with Microsoft Office

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

Java

C and C++

C++

Server operating systems

All OS with a Java VM

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

Typing

predefined data types such as float or date

yes

Numeric data

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

APIs and other access methods

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
DAO
ODBC
OLE DB

HTTP API

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

since Access 2010 using the ACE-engine

Triggers

yes

by using the 'percolation' feature

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate 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

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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.

Memcached and Redis integration

yes

User concepts

Access control

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

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

simple rights management via user accounts

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.