DBMS > Datomic vs. Hawkular Metrics vs. IBM Cloudant vs. OrigoDB

System Properties Comparison Datomic vs. Hawkular Metrics vs. IBM Cloudant vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Database as a Service offering based on Apache CouchDB

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Time Series DBMS

Document store

Document store
Object oriented DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

www.datomic.com

www.hawkular.org

www.ibm.com/products/cloudant

origodb.com

Technical documentation

docs.datomic.com

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

cloud.ibm.com/docs/Cloudant

origodb.com/docs

Developer

Cognitect

Community supported by Red Hat

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Robert Friberg et al

Initial release

2012

2014

2010

2009

under the name LiveDB

Current release

1.0.7075, December 2023

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

commercial

Open Source

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, Clojure

Java

Erlang

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

HTTP REST

RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

Supported programming languages

Clojure
Java

Go
Java
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net

Server-side scripts

Stored procedures

yes

Transaction Functions

View functions (Map-Reduce) in JavaScript

yes

Triggers

By using transaction functions

yes

via Hawkular Alerting

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

based on Cassandra

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

Write ahead log

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users can be defined per database

Role based authorization

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

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

James Dixon Imagines A Data Lake That Matters
26 January 2015, Forbes

Zoona Case Study
16 December 2017, AWS Blog

provided by Google News

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

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

Share this page