DBMS > GeoMesa vs. LeanXcale vs. Riak TS vs. Teradata

System Properties Comparison GeoMesa vs. LeanXcale vs. Riak TS vs. Teradata

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.

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Spatial DBMS

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

www.geomesa.org

www.leanxcale.com

www.teradata.com

Technical documentation

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

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

docs.teradata.com

Developer

CCRi and others

LeanXcale

Open Source, formerly Basho Technologies

Teradata

Initial release

2014

2015

1984

Current release

5.0.0, May 2024

3.0.0, September 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

commercial

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

Erlang

Server operating systems

Linux
OS X

hosted
Linux

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

restricted

yes

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

SQL

Support of SQL

yes

through Apache Derby

yes, limited

yes

SQL 2016 + extensions

APIs and other access methods

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

HTTP API
Native Erlang Interface

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

Supported programming languages

C
Java
Scala

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
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

Erlang

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

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

depending on storage layer

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

yes

Transaction concepts

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

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

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

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

show all

Recent citations in the news

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Is There Now An Opportunity In Teradata Corporation (NYSE:TDC)?
28 May 2024, Yahoo Finance

Corient Private Wealth LLC Reduces Stock Holdings in Teradata Co. (NYSE:TDC)
30 May 2024, Defense World

Corient Private Wealth LLC Sells 41,270 Shares of Teradata Co. (NYSE:TDC)
30 May 2024, MarketBeat

Should You Be Excited About Teradata Corporation's (NYSE:TDC) 78% Return On Equity?
27 May 2024, Simply Wall St

Lakehouse dam breaks after departure of long-time Teradata CTO
1 May 2024, The Register

provided by Google News

Share this page