DBMS > EJDB vs. Hawkular Metrics vs. Prometheus vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison EJDB vs. Hawkular Metrics vs. Prometheus vs. SAP Advantage Database Server vs. Snowflake

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Open-source Time Series DBMS and monitoring system

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

Primary database model

Document store

Time Series DBMS

Relational DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/Softmotions/ejdb

www.hawkular.org

prometheus.io

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

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

prometheus.io/docs

docs.snowflake.net/manuals/index.html

Developer

Softmotions

Community supported by Red Hat

Sybase, SAP

Snowflake Computing Inc.

Initial release

2012

2014

2015

1993

2014

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

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

Server operating systems

server-less

Linux
OS X
Windows

Linux
Windows

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Numeric data only

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.

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

in-process shared library

HTTP REST

RESTful HTTP/JSON API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Go
Java
Python
Ruby

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

via Hawkular Alerting

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

yes

by Federation

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

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

none

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

caching of (temporary) tables can be configured

User concepts

Access control

fine grained access rights according to SQL-standard

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

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.