DBMS > EJDB vs. Hawkular Metrics vs. Vitess vs. Warp 10

System Properties Comparison EJDB vs. Hawkular Metrics vs. Vitess vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

github.com/Softmotions/ejdb

www.hawkular.org

vitess.io

www.warp10.io

Technical documentation

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

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

vitess.io/docs

www.warp10.io/content/02_Getting_started

Developer

Softmotions

Community supported by Red Hat

The Linux Foundation, PlanetScale

SenX

Initial release

2012

2014

2013

2015

Current release

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Apache Version 2.0, commercial licenses available

Open Source

Apache License 2.0

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

Server operating systems

server-less

Linux
OS X
Windows

Docker
Linux
macOS

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

in-process shared library

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

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

Go
Java
Python
Ruby

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

yes

proprietary syntax

yes

WarpScript

Triggers

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Time Series Databases Software Market - A comprehensive study by Key Players | Warp 10, Amazon Timestream ...
6 February 2020, openPR

Time Series Databases Software market latest trends, CAGR, and forecast till 2026 | eSherpa Market Reports
13 April 2020, openPR

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
12 June 2024, Amoré

provided by Google News

Share this page