DBMS > Microsoft Access vs. Riak KV vs. SiteWhere vs. SQLite

System Properties Comparison Microsoft Access vs. Riak KV vs. SiteWhere vs. SQLite

Please select another system to include it in the comparison.

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

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store

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

Time Series DBMS

Relational DBMS

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

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

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

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

developer.microsoft.com/en-us/access

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

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

Microsoft

OpenSource, formerly Basho Technologies

SiteWhere

Dwayne Richard Hipp

Initial release

1992

2009

2010

2000

Current release

1902 (16.0.11328.20222), March 2019

3.2.0, December 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Erlang

Java

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
OS X

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

restricted

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

HTTP API
Native Erlang Interface

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Erlang

Triggers

yes

since Access 2010 using the ACE-engine

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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

yes, using Riak Security

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.