DBMS > Apache Drill vs. Graph Engine vs. Riak KV vs. TempoIQ

System Properties Comparison Apache Drill vs. Graph Engine vs. Riak KV vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Distributed, fault tolerant key-value store

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Document store
Relational DBMS

Graph DBMS
Key-value store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

drill.apache.org

www.graphengine.io

tempoiq.com (offline)

Technical documentation

drill.apache.org/docs

www.graphengine.io/docs/manual

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Apache Software Foundation

Microsoft

OpenSource, formerly Basho Technologies

TempoIQ

Initial release

2012

2010

2009

2012

Current release

1.20.3, January 2023

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

Open Source

Apache version 2, commercial enterprise edition

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

.NET and C

Erlang

Server operating systems

Linux
OS X
Windows

.NET

Linux
OS X

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

restricted

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

C++

C#
C++
F#
Visual Basic

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

yes, using Riak Security

simple authentication-based access control

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

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Using Apache Iceberg for Developing Modern Data Tables
3 October 2023, Open Source For You

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

provided by Google News

Trinity
2 June 2023, Microsoft

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

How Google and Microsoft taught search to "understand" the Web
6 June 2012, Ars Technica

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page