DBMS > Hawkular Metrics vs. Microsoft Access vs. SiriDB vs. Snowflake vs. Warp 10

System Properties Comparison Hawkular Metrics vs. Microsoft Access vs. SiriDB vs. Snowflake vs. Warp 10

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

Open Source Time Series DBMS

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.hawkular.org

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

siridb.com

www.snowflake.com

www.warp10.io

Technical documentation

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

developer.microsoft.com/en-us/access

docs.siridb.com

docs.snowflake.net/manuals/index.html

www.warp10.io/content/02_Getting_started

Developer

Community supported by Red Hat

Microsoft

Cesbit

Snowflake Computing Inc.

SenX

Initial release

2014

1992

2017

2014

2015

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

MIT License

commercial

Open Source

Apache License 2.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

Java

C++

Java

Server operating systems

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

Numeric data

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

yes

but not compliant to any SQL standard

yes

APIs and other access methods

HTTP REST

ADO.NET
DAO
ODBC
OLE DB

HTTP API

CLI Client
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

Go
Java
Python
Ruby

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

yes

WarpScript

Triggers

yes

via Hawkular Alerting

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

based on Cassandra

none

Sharding

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

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

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

simple rights management via user accounts

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.