DBMS > 4D vs. GeoMesa vs. Infobright vs. TimesTen vs. XTDB

System Properties Comparison 4D vs. GeoMesa vs. Infobright vs. TimesTen vs. XTDB

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.

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

In-Memory RDBMS compatible to Oracle

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.4d.com

www.geomesa.org

ignitetech.com/softwarelibrary/infobrightdb

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

developer.4d.com

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

docs.oracle.com/database/timesten-18.1

www.xtdb.com/docs

Developer

4D, Inc

CCRi and others

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle, TimesTen Performance Software, HP

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

Juxt Ltd.

Initial release

1984

2014

2005

1998

2019

Current release

v20, April 2023

5.0.0, May 2024

11 Release 2 (11.2.2.8.0)

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

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

commercial

Open Source

MIT License

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

Clojure

Server operating systems

OS X
Windows

Linux
Windows

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

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

close to SQL 92

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

ADO.NET
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST
JDBC

Supported programming languages

4D proprietary IDE
PHP

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

C
C++
Java
PL/SQL

Clojure
Java

Server-side scripts

Stored procedures

yes

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

Source-replica replication

Multi-source replication
Source-replica replication

yes, each node contains all data

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

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Share this page