DBMS > 4D vs. GeoMesa vs. MySQL vs. TimesTen

System Properties Comparison 4D vs. GeoMesa vs. MySQL vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Widely used open source RDBMS

In-Memory RDBMS compatible to Oracle

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	1.35
Rank	#165	Overall
	#75	Relational DBMS

Website

www.4d.com

www.geomesa.org

www.mysql.com

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

Technical documentation

developer.4d.com

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

dev.mysql.com/doc

docs.oracle.com/database/timesten-18.1

Developer

4D, Inc

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

Oracle, TimesTen Performance Software, HP

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

Initial release

1984

2014

1995

1998

Current release

v20, April 2023

4.0.5, February 2024

8.3.0, January 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

C and C++

Server operating systems

OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

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

with proprietary extensions

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

4D proprietary IDE
PHP

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

proprietary syntax

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

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

Immediate Consistency

depending on storage layer

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Users and groups

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or 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.