DBMS > 4D vs. Apache Kylin vs. GeoMesa vs. Riak TS vs. ToroDB

System Properties Comparison 4D vs. Apache Kylin vs. GeoMesa vs. Riak TS vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Application development environment with integrated database management system

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.4d.com

kylin.apache.org

www.geomesa.org

github.com/torodb/server

Technical documentation

developer.4d.com

kylin.apache.org/docs

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

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

Developer

4D, Inc

Apache Software Foundation, originally contributed from eBay Inc

CCRi and others

Open Source, formerly Basho Technologies

8Kdata

Initial release

1984

2015

2014

2015

2016

Current release

v20, April 2023

3.1.0, July 2020

5.0.0, May 2024

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

AGPL-V3

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

Erlang

Java

Server operating systems

OS X
Windows

Linux

Linux
OS X

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

yes

close to SQL 92

ANSI SQL for queries (using Apache Calcite)

yes, limited

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

4D proprietary IDE
PHP

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

Server-side scripts

Stored procedures

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

selectable replication factor

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

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

User concepts

Access control

Users and groups

yes

depending on the DBMS used for storage

Access rights for users and roles

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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Overhauling Apache Kylin for the cloud
18 November 2021, InfoWorld

eBay's Kylin Becomes a Top-Level Apache Open Source Project
9 December 2015, eBay Inc.

The Apache Software Foundation Announces Apache™ Kylin™ as a Top-Level Project
8 December 2015, GlobeNewswire

Bringing interactive BI to big data – O'Reilly
1 May 2017, oreilly.com

Distributed OLAPer Kyligence accelerates core engine, adds real-time data support – Blocks and Files
10 August 2021, Blocks & Files

provided by Google News

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

provided by Google News

Share this page