DBMS > GeoMesa vs. Heroic vs. Oracle Berkeley DB vs. Tibero

System Properties Comparison GeoMesa vs. Heroic vs. Oracle Berkeley DB vs. Tibero

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used in-process key-value store

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Spatial DBMS

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

www.geomesa.org

github.com/spotify/heroic

www.oracle.com/database/technologies/related/berkeleydb.html

us.tmaxsoft.com/products/tibero

Technical documentation

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

spotify.github.io/heroic

docs.oracle.com/cd/E17076_05/html/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

CCRi and others

Spotify

Oracle

originally developed by Sleepycat, which was acquired by Oracle

TmaxSoft

Initial release

2014

1994

2003

Current release

5.0.0, May 2024

18.1.40, May 2020

6, April 2015

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

commercial license available

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

Java

C, Java, C++ (depending on the Berkeley DB edition)

C and Assembler

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

AIX
HP-UX
Linux
Solaris
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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

Persistent Stored Procedure (PSM)

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Source-replica replication

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

Eventual Consistency
Immediate Consistency

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

planned for next version

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, Datanami

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Oracle buys Sleepycat Software
14 February 2006, MarketWatch

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

provided by Google News

ArkData to Officially Support Domestic Database 'Tibero 7'
23 April 2024, BusinessKorea

How to Succeed at Large-Scale Mainframe Replatforming with TmaxSoft OpenFrame on AWS | Amazon Web Services
2 August 2022, AWS Blog

TmaxData to supply database management software to Hyundai, Kia
12 June 2019, 코리아타임스

CTOS strengthens its database management system with TmaxSoft
20 December 2016, Digital News Asia

Open-source DBMS becoming battleground of public cloud
17 May 2022, Etnews

provided by Google News

Share this page