DBMS > Apache Impala vs. Heroic vs. KeyDB vs. OrigoDB

System Properties Comparison Apache Impala vs. Heroic vs. KeyDB vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

Document store
Object oriented DBMS

Secondary database models

Document store

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

impala.apache.org

github.com/spotify/heroic

github.com/Snapchat/KeyDB
keydb.dev

origodb.com

Technical documentation

impala.apache.org/impala-docs.html

spotify.github.io/heroic

docs.keydb.dev

origodb.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Spotify

EQ Alpha Technology Ltd.

Robert Friberg et al

Initial release

2013

2014

2019

2009

under the name LiveDB

Current release

4.1.0, June 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

BSD-3

Open Source

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

C++

Java

C++

Server operating systems

Linux

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

via Elasticsearch

yes

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Lua

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

Write ahead log

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 for users, groups and roles

based on Apache Sentry and Kerberos

simple password-based access control and ACL

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

Apache Impala 4 Supports Operator Multi-Threading
29 July 2021, iProgrammer

Apache Impala becomes Top-Level Project
28 November 2017, SDTimes.com

Cloudera Bringing Impala to AWS Cloud
28 November 2017, Datanami

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

Updates & Upserts in Hadoop Ecosystem with Apache Kudu
27 October 2017, KDnuggets

provided by Google News

Snap snaps up database developer KeyDB to make its infrastructure more snappy
12 May 2022, TechCrunch

Introducing Garnet – an open-source, next-generation, faster cache-store for accelerating applications and services
18 March 2024, Microsoft

Microsoft open-sources unique “Garnet” cache-store; a Redis rival?
19 March 2024, The Stack

Dragonfly 0.13 Database Adds Experimental SSD-Based Data Tiering, More SIMD Work
2 January 2023, Phoronix

Beyond the mainstream database offerings
26 March 2020, TechCentral.ie

provided by Google News

Share this page