DBMS > atoti vs. DataFS vs. Google BigQuery vs. Microsoft Access vs. Newts

System Properties Comparison atoti vs. DataFS vs. Google BigQuery vs. Microsoft Access vs. Newts

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Time Series DBMS based on Cassandra

Primary database model

Object oriented DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Graph DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

atoti.io

newdatabase.com

cloud.google.com/bigquery

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

opennms.github.io/newts

Technical documentation

docs.atoti.io

dev.mobiland.com/Overview.xsp

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

github.com/OpenNMS/newts/wiki

Developer

ActiveViam

Mobiland AG

Google

Microsoft

OpenNMS Group

Initial release

2018

2010

1992

2014

Current release

1.1.263, October 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

free versions available

commercial

Bundled with Microsoft Office

Open Source

Apache 2.0

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

Windows

hosted

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Windows

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

Multidimensional Expressions (MDX)

yes

but not compliant to any SQL standard

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

HTTP REST
Java API

Supported programming languages

.Net
C
C#
C++
VB.Net

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Java

Server-side scripts

Stored procedures

Python

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

no, except callback-events from server when changes happened

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Proprietary Sharding system

none

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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, multi-version concurrency control (MVCC)

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.

yes

User concepts

Access control

Windows-Profile

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.