DBMS > Coveo vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. SiteWhere

System Properties Comparison Coveo vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

M2M integration platform for persisting/querying time series data

Primary database model

Search engine

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

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	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.coveo.com

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

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

Technical documentation

docs.coveo.com

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

Developer

Coveo

Microsoft

SiteWhere

Initial release

2012

1992

2014

2010

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

Common Public Attribution License Version 1.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

C++

Java

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Windows

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

predefined scheme

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

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

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

HTTP REST

Supported programming languages

C#
Java
JavaScript
Python

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

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

yes

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

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.

User concepts

Access control

granular access controls, API key management, content filters

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

Access rights can be defined down to the item level

Users with fine-grained authorization concept

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.