DBMS > Apache Druid vs. GeoMesa vs. RavenDB vs. Transbase

System Properties Comparison Apache Druid vs. GeoMesa vs. RavenDB vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Open Source Operational and Transactional Enterprise NoSQL Document Database

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Spatial DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

druid.apache.org

www.geomesa.org

ravendb.net

www.transaction.de/en/products/transbase.html

Technical documentation

druid.apache.org/docs/latest/design

www.geomesa.org/documentation/stable/user/index.html

ravendb.net/docs

www.transaction.de/en/products/transbase/features.html

Developer

Apache Software Foundation and contributors

CCRi and others

Hibernating Rhinos

Transaction Software GmbH

Initial release

2012

2014

2010

1987

Current release

29.0.1, April 2024

5.0.0, May 2024

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache License 2.0

Open Source

AGPL version 3, commercial license available

commercial

free development license

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

Scala

C and C++

Server operating systems

Linux
OS X
Unix

Linux
macOS
Raspberry Pi
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

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

yes

SQL

Support of SQL

SQL for querying

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

depending on storage layer

Multi-source 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

depending on storage layer

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

yes

Concurrency

Support for concurrent manipulation of data

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.

depending on storage layer

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

yes

depending on the DBMS used for storage

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Apache Druid Wins Best Big Data Product in the 2023 BigDATAwire Readers' Choice Awards
26 January 2024, Datanami

'Lucifer' Botnet Turns Up the Heat on Apache Hadoop Servers
21 February 2024, Dark Reading

New DDoS malware Attacking Apache big-data stack, Hadoop, & Druid Servers
26 February 2024, GBHackers

Apache Druid Takes Its Place In The Pantheon Of Databases
16 June 2022, The Next Platform

How to connect DataGrip to Apache Druid | by Zisis Flokas
18 October 2021, Towards Data Science

provided by Google News

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

RavenDB Adds Graph Queries
15 May 2019, Datanami

Review: NoSQL database RavenDB
20 March 2019, TechGenix

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

provided by Google News

Share this page