DBMS > GeoMesa vs. Infobright vs. Postgres-XL vs. RethinkDB

System Properties Comparison GeoMesa vs. Infobright vs. Postgres-XL vs. RethinkDB

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.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Spatial DBMS

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Website

www.geomesa.org

ignitetech.com/softwarelibrary/infobrightdb

www.postgres-xl.org

rethinkdb.com

Technical documentation

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

www.postgres-xl.org/documentation

rethinkdb.com/docs

Developer

CCRi and others

Ignite Technologies Inc.; formerly InfoBright Inc.

The Linux Foundation

since July 2017

Initial release

2014

2005

2014

since 2012, originally named StormDB

2009

Current release

5.0.0, May 2024

10 R1, October 2018

2.4.1, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Mozilla public license

Open Source

Apache Version 2

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++

Server operating systems

Linux
Windows

Linux
macOS

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

XML type, but no XML query functionality

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

horizontal partitioning

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

yes

users and table-level permissions

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

Meet some database management systems you are likely to hear more about in the future
4 August 2014, Paul Andlinger

show all

Recent citations in the news

An introduction to building realtime apps with RethinkDB
9 July 2022, devmio

How to Use RethinkDB with Node.js Applications — SitePoint
16 December 2015, SitePoint

Stripe acquires team behind NoSQL database startup RethinkDB
5 October 2016, VentureBeat

RethinkDB is dead, and MongoDB isn't what killed it
24 January 2017, TechRepublic

Open Source Horizon Claims Edge over Google's Firebase Mobile Back-End -- ADTmag
23 May 2016, ADT Magazine

provided by Google News

Share this page