DBMS > IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. TDengine vs. Vertica

System Properties Comparison IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. TDengine vs. Vertica

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

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

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS and big data platform

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS

Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.60
Rank	#107	Overall
	#8	Time Series DBMS

Score	10.68
Rank	#43	Overall
	#27	Relational DBMS

Website

www.ibm.com/products/cloudant

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

azure.microsoft.com/services/cosmos-db

github.com/taosdata/TDengine
tdengine.com

www.vertica.com

Technical documentation

cloud.ibm.com/docs/Cloudant

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

docs.tdengine.com

vertica.com/documentation

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

TDEngine, previously Taos Data

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2010

1992

2014

2019

2005

Current release

1902 (16.0.11328.20222), March 2019

3.0, August 2022

12.0.3, January 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

GPL V3, also commercial editions available

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

C++

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

hosted

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

Standard SQL with extensions for time-series applications

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
RESTful HTTP API

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

since Access 2010 using the ACE-engine

JavaScript

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

yes, via alarm monitoring

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

Implicit feature of the cloud service

yes

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

User concepts

Access control

Access rights for users can be defined per database

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

Access rights can be defined down to the item level

yes

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

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

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

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

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

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

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» 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

Cost-based models and subscription-based models are both available. One license is...
» more

News

Compare InfluxDB vs. TDengine
19 April 2024

Why We Need the Next Generation Data Historian
15 April 2024

Is Closed-Source Software Really More Secure?
8 April 2024

Developers: Stop Donating Your Work to Cloud Service Providers!
28 March 2024

Compare AVEVA Data Hub vs. TDengine
19 March 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.