DBMS > Microsoft Access vs. Oracle Coherence vs. Snowflake vs. SwayDB vs. TDengine

System Properties Comparison Microsoft Access vs. Oracle Coherence vs. Snowflake vs. SwayDB vs. TDengine

Editorial information provided by DB-Engines

Name

Description

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

Oracles in-memory data grid solution

Cloud-based data warehousing service for structured and semi-structured data

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Time Series DBMS and big data platform

Primary database model

Secondary database models

Relational DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	2.68
Rank	#106	Overall
	#9	Time Series DBMS

Website

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

www.oracle.com/java/coherence

www.snowflake.com

swaydb.simer.au

github.com/taosdata/TDengine
tdengine.com

Technical documentation

developer.microsoft.com/en-us/access

docs.oracle.com/en/middleware/standalone/coherence

docs.snowflake.net/manuals/index.html

docs.tdengine.com

Developer

Microsoft

Oracle

Snowflake Computing Inc.

Simer Plaha

TDEngine, previously Taos Data

Initial release

1992

2007

2014

2018

2019

Current release

1902 (16.0.11328.20222), March 2019

14.1, August 2023

3.0, August 2022

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

GNU Affero GPL V3.0

Open Source

AGPL V3, also commercial editions 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

C++

Java

Scala

Server operating systems

Windows

Not a real database server, but making use of DLLs

All OS with a Java VM

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

Standard SQL with extensions for time-series applications

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

JCache
JPA
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
RESTful HTTP API

Supported programming languages

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

.Net
C++
Java

JavaScript (Node.js)
Python

Java
Kotlin
Scala

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

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

Live Events

similar concept for controling cloud resources

yes, via alarm monitoring

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with selectable consistency level

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

configurable

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

optionally

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

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

authentification to access the cache via certificates or http basic authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

More information provided by the system vendor

Specific characteristics

TDengine™ is a next generation data historian purpose-built for Industry 4.0 and...
» more

Competitive advantages

High Performance at any Scale: TDengine is purpose-built for handling massive industrial...
» more

Typical application scenarios

TDengine is designed for Industrial IoT scenarios, including: Manufacturing Connected...
» more

Market metrics

TDengine has garnered over 22,500 stars on GitHub and is used in over 50 countries...
» more

Licensing and pricing models

TDengine OSS is an open source, cloud native time series database. It includes built-in...
» more

News

Mastering Memory Leak Detection in TDengine
31 May 2024

Seamless Data Integration from MQTT and InfluxDB to TDengine
22 May 2024

Solving Long Query Performance Bottlenecks
22 May 2024

What Is Predictive Maintenance?
17 May 2024

Can Typical Time-Series Databases Replace Data Historians?
8 May 2024

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.