DBMS > Hawkular Metrics vs. LevelDB vs. Microsoft SQL Server vs. MySQL

System Properties Comparison Hawkular Metrics vs. LevelDB vs. Microsoft SQL Server vs. MySQL

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.

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Microsofts flagship relational DBMS

Widely used open source RDBMS

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

Score	2.75
Rank	#107	Overall
	#19	Key-value stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

www.hawkular.org

github.com/google/leveldb

www.microsoft.com/en-us/sql-server

www.mysql.com

Technical documentation

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

github.com/google/leveldb/blob/main/doc/index.md

learn.microsoft.com/en-US/sql/sql-server

dev.mysql.com/doc

Developer

Community supported by Red Hat

Google

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2011

1989

1995

Current release

1.23, February 2021

SQL Server 2022, November 2022

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

commercial

restricted free version is available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++

C and C++

Server operating systems

Linux
OS X
Windows

Illumos
Linux
OS X
Windows

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

HTTP REST

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

proprietary syntax

Triggers

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

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

with automatic compression on writes

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

fine grained access rights according to SQL-standard

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.