DBMS > Alibaba Cloud MaxCompute vs. ClickHouse vs. Faircom EDGE vs. Microsoft Access vs. Snowflake

System Properties Comparison Alibaba Cloud MaxCompute vs. ClickHouse vs. Faircom EDGE vs. Microsoft Access vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

MaxCompute (previously known as ODPS) is a general purpose, fully managed, multi-tenancy data processing platform for large-scale data warehousing

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

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

Primary database model

Relational DBMS

a graph-processing framework is available with the graphs being stored in tables

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.78
Rank	#221	Overall
	#102	Relational DBMS

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	0.03
Rank	#380	Overall
	#59	Key-value stores
	#157	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

www.alibabacloud.com/product/maxcompute

clickhouse.com

www.faircom.com/products/faircom-edge

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

www.snowflake.com

Technical documentation

www.alibabacloud.com/help/en/maxcompute

clickhouse.com/docs

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Alibaba

Clickhouse Inc.

FairCom Corporation

Microsoft

Snowflake Computing Inc.

Initial release

2016

1979

1992

2014

Current release

v24.3.2.23-lts, April 2024

V3, October 2020

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Restricted, free version available

commercial

Bundled with Microsoft Office

commercial

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.

ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

ANSI C, C++

C++

Server operating systems

hosted

FreeBSD
Linux
macOS

Android
Linux

ARM, x86
Raspbian
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

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

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

Close to ANSI SQL (SQL/JSON + extensions)

yes

ANSI SQL queries

yes

but not compliant to any SQL standard

yes

APIs and other access methods

Fluentd
Flume
MaxCompute Console

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Java

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Java

yes

.Net, JavaScript, C/C++

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

key based and custom

File partitioning

Customizable business rules for partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

Access rights for users and roles

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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

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

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.