DBMS > Axibase vs. Brytlyt vs. GeoSpock vs. Google BigQuery vs. Microsoft Access

System Properties Comparison Axibase vs. Brytlyt vs. GeoSpock vs. Google BigQuery vs. Microsoft Access

Editorial information provided by DB-Engines

Name

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

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

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

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

axibase.com/docs/atsd/finance

brytlyt.io

geospock.com

cloud.google.com/bigquery

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

Technical documentation

docs.brytlyt.io

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

Developer

Axibase Corporation

Brytlyt

GeoSpock

Google

Microsoft

Initial release

2013

2016

2010

1992

Current release

15585

5.0, August 2023

2.0, September 2019

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Bundled with Microsoft Office

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, C++ and CUDA

Java, Javascript

C++

Server operating systems

Linux

Linux
OS X
Windows

hosted

Windows

Not a real database server, but making use of DLLs

Data scheme

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

SQL-like query language

yes

ANSI SQL for query only (using Presto)

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

user defined functions

in PL/pgSQL

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

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)

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

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.