DBMS > Geode vs. Hawkular Metrics vs. Microsoft SQL Server vs. SAP SQL Anywhere

System Properties Comparison Geode vs. Hawkular Metrics vs. Microsoft SQL Server vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Microsofts flagship relational DBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Website

geode.apache.org

www.hawkular.org

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

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

geode.apache.org/docs

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

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Community supported by Red Hat

Microsoft

SAP

formerly Sybase

Initial release

2002

2014

1989

1992

Current release

1.1, February 2017

SQL Server 2022, November 2022

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

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++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Linux
Windows

AIX
HP-UX
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

SQL-like query language (OQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST

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

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

Go
Java
Python
Ruby

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Cache Event Listeners

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

based on Cassandra

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

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

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights per client and object definable

fine grained access rights according to SQL-standard

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.