DBMS > GeoMesa vs. RavenDB vs. Teradata vs. WakandaDB

System Properties Comparison GeoMesa vs. RavenDB vs. Teradata vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

A hybrid cloud data analytics software platform (Teradata Vantage)

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

Technical documentation

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

ravendb.net/docs

docs.teradata.com

wakanda.github.io/doc

Developer

CCRi and others

Hibernating Rhinos

Teradata

Wakanda SAS

Initial release

2014

2010

1984

2012

Current release

5.0.0, May 2024

5.4, July 2022

Teradata Vantage 1.0 MU2, January 2019

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

AGPL version 3, commercial license available

commercial

Open Source

AGPLv3, extended commercial license available

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

Scala

C++, JavaScript

Server operating systems

Linux
macOS
Raspberry Pi
Windows

hosted
Linux

Linux
OS X
Windows

Data scheme

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.

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like query language (RQL)

yes

SQL 2016 + extensions

APIs and other access methods

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

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

RESTful HTTP API

Supported programming languages

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

JavaScript

Server-side scripts

Stored procedures

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

yes

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

Teradata is the most popular data warehouse DBMS
2 April 2013, Paul Andlinger

show all

Recent citations in the 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

Is There Now An Opportunity In Teradata Corporation (NYSE:TDC)?
11 June 2024, Simply Wall St

Redwood Investment Management LLC Acquires 103,761 Shares of Teradata Co. (NYSE:TDC)
11 June 2024, MarketBeat

Teradata Stock Analysis: Don't Let the Amazon News Fool You Into Buying Now
10 June 2024, InvestorPlace

Teradata to Present at Upcoming Investor Conference
6 June 2024, Business Wire

Teradata (TDC) Down 2.5% Since Last Earnings Report: Can It Rebound?
5 June 2024, Yahoo Finance

provided by Google News

Share this page