DBMS > CrateDB vs. Microsoft Access vs. Riak KV vs. Snowflake

System Properties Comparison CrateDB vs. Microsoft Access vs. Riak KV vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

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

Distributed, fault tolerant key-value store

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

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.71
Rank	#227	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#10	Vector DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

cratedb.com

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

www.snowflake.com

Technical documentation

cratedb.com/docs

developer.microsoft.com/en-us/access

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

Developer

Crate

Microsoft

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2013

1992

2009

2014

Current release

1902 (16.0.11328.20222), March 2019

3.2.0, December 2022

License

Commercial or Open Source

Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache version 2, commercial enterprise edition

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.

Implementation language

Java

C++

Erlang

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Windows

Not a real database server, but making use of DLLs

Linux
OS X

hosted

Data scheme

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

yes

schema-free

yes

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

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

restricted

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

but not compliant to any SQL standard

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions (Javascript)

yes

since Access 2010 using the ACE-engine

Erlang

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Read-after-write consistency on record level

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

ACID

but no files for transaction logging

ACID

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

rights management via user accounts

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

yes, using Riak Security

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.