DBMS > Hawkular Metrics vs. Microsoft Access vs. MySQL vs. PouchDB

System Properties Comparison Hawkular Metrics vs. Microsoft Access vs. MySQL vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

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

Widely used open source RDBMS

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	0.01
Rank	#377	Overall
	#39	Time Series DBMS

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.18
Rank	#114	Overall
	#21	Document stores

Website

www.hawkular.org

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

www.mysql.com

pouchdb.com

Technical documentation

www.hawkular.org/hawkular-metrics/docs/user-guide

developer.microsoft.com/en-us/access

dev.mysql.com/doc

pouchdb.com/guides

Developer

Community supported by Red Hat

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Initial release

2014

1992

1995

2012

Current release

1902 (16.0.11328.20222), March 2019

9.0.0, July 2024

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

Java

C++

C and C++

JavaScript

Server operating systems

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

schema-free

yes

schema-free

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

via views

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

HTTP REST

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

Go
Java
Python
Ruby

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

View functions in JavaScript

Triggers

yes

via Hawkular Alerting

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Users with fine-grained authorization concept

no user groups or roles

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.