DBMS > GeoMesa vs. OceanBase vs. PostGIS vs. TerarkDB

System Properties Comparison GeoMesa vs. OceanBase vs. PostGIS vs. TerarkDB

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 distributed, high available RDBMS compatible with Oracle and MySQL

Spatial extension of PostgreSQL

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Document store
Wide column store

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.66
Rank	#147	Overall
	#68	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.geomesa.org

en.oceanbase.com

postgis.net

github.com/bytedance/terarkdb

Technical documentation

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

en.oceanbase.com/docs/oceanbase-database

postgis.net/documentation

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

CCRi and others

OceanBase

previously Alibaba and Ant Group

ByteDance, originally Terark

Initial release

2014

2010

2005

2016

Current release

5.0.0, May 2024

4.3.0, April 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Commercial license available

Open Source

GPL v2.0

commercial

restricted open source version 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++

Server operating systems

Linux

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

C++ API
Java API

Supported programming languages

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

C++
Java

Server-side scripts

Stored procedures

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication using Paxos

yes

based on PostgreSQL

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

Immediate Consistency

Foreign keys

Referential integrity

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

Access rights for users, groups and roles according to SQL-standard

yes

based on PostgreSQL

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

OceanBase Inks Agreement with NTU Singapore in Database Optimization and Green Computing Advancements
31 January 2024, PR Newswire

Ant Group Will Cut Foreign Investors Out of Fast-Growing Database Business
22 August 2023, The Information

How Southeast Asia's Leading e-Wallets Saved Up to 40% in Database Costs - Fintech Singapore
25 March 2024, Fintech News Singapore

Haidilao’s 6-step recipe for successful digital transformation with OceanBase
4 August 2023, Tech in Asia

Alibaba's OceanBase distributed database aims at markets outside China
16 August 2022, InfoWorld

provided by Google News

Share this page