DBMS > GeoMesa vs. OpenEdge vs. Percona Server for MongoDB vs. TimesTen

System Properties Comparison GeoMesa vs. OpenEdge vs. Percona Server for MongoDB vs. TimesTen

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.

Application development environment with integrated database management system

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

www.geomesa.org

www.progress.com/openedge

www.percona.com/mongodb/software/percona-server-for-mongodb

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

Technical documentation

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

documentation.progress.com/output/ua/OpenEdge_latest

docs.percona.com/percona-distribution-for-mongodb

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

CCRi and others

Progress Software Corporation

Percona

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2014

1984

2015

1998

Current release

5.0.1, July 2024

OpenEdge 12.2, March 2020

3.4.10-2.10, November 2017

Release 22.1

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPL Version 2

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

C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Linux

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

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

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

JDBC
ODBC

proprietary protocol using JSON

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

Progress proprietary ABL (Advanced Business Language)

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

yes

JavaScript

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

since Version 11.4

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

by means of logfiles and checkpoints

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

via In-Memory Engine

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Users and groups

Access rights for users and roles

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

Recent citations in the news

What's New in OpenEdge 12.8
15 April 2024, release.nl

4 sources of latency and how to avoid them
1 November 2017, InfoWorld

provided by Google News

Percona launches management system aimed at open-source databases
17 May 2022, The Register

Percona Everest sets databases free
17 September 2024, Techzine Europe

Is database-as-a-service in Percona’s future?
23 May 2022, VentureBeat

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

The essential guide to MongoDB security
2 February 2017, InfoWorld

provided by Google News

Oracle starts peddling Exalytics in-memory appliance
12 March 2012, The Register

SAP S&D Benchmark - The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
8 May 2015, AnandTech

provided by Google News

Share this page