DBMS > 4D vs. Atos Standard Common Repository vs. GeoMesa vs. IRONdb vs. XTDB

System Properties Comparison 4D vs. Atos Standard Common Repository vs. GeoMesa vs. IRONdb vs. XTDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Application development environment with integrated database management system

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Relational DBMS

Document store
Key-value store

Spatial DBMS

Time Series DBMS

Document store

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.4d.com

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.geomesa.org

www.circonus.com/solutions/time-series-database/

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

Technical documentation

developer.4d.com

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

docs.circonus.com/irondb/category/getting-started

www.xtdb.com/docs

Developer

4D, Inc

Atos Convergence Creators

CCRi and others

Circonus LLC.

Juxt Ltd.

Initial release

1984

2016

2014

2017

2019

Current release

v20, April 2023

1703

4.0.5, February 2024

V0.10.20, January 2018

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

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

Java

Scala

C and C++

Clojure

Server operating systems

OS X
Windows

Linux

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

Data scheme

yes

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

yes

text, numeric, histograms

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

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language (Circonus Analytics Query Language: CAQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

HTTP API

HTTP REST
JDBC

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Clojure
Java

Server-side scripts

Stored procedures

yes

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

depending on storage layer

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

depending on storage layer

configurable replication factor, datacenter aware

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

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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.

yes

depending on storage layer

User concepts

Access control

Users and groups

LDAP bind authentication

yes

depending on the DBMS used for storage

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

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Application observability firm Apica buys telemetry data startup Circonus and adds more funding
21 February 2024, SiliconANGLE News

Apica Acquires Telemetry Data Management Pioneer Circonus And Lands New Funding
22 February 2024, Datanami

Apica gets $6 million in funding and buys Circonus -
21 February 2024, Enterprise Times

provided by Google News

Share this page