DBMS > 4D vs. Atos Standard Common Repository vs. Geode vs. PostGIS vs. QuestDB

System Properties Comparison 4D vs. Atos Standard Common Repository vs. Geode vs. PostGIS vs. QuestDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed 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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Spatial extension of PostgreSQL

A high performance open source SQL database for time series data

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Spatial DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	2.83
Rank	#106	Overall
	#55	Relational DBMS

Score	1.70
Rank	#137	Overall
	#26	Key-value stores

Score	31.68
Rank	#28	Overall
	#1	Spatial DBMS

Score	1.24
Rank	#155	Overall
	#12	Time Series DBMS

Website

www.4d.com

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

geode.apache.org

postgis.net

questdb.io

Technical documentation

livedoc.4d.com

geode.apache.org/docs

postgis.net/documentation

questdb.io/docs/introduction

Developer

4D, Inc

Atos Convergence Creators

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

QuestDB Limited

Initial release

1984

2016

2002

2005

2014

Current release

v18 R5, January 2021

1703

1.1, February 2017

3.2.1, February 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL v2.0

Open Source

Apache 2.0

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

Server operating systems

OS X
Windows

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Windows

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

schema-free via InfluxDB Line Protocol

Typing

predefined data types such as float or date

yes

optional

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

SQL-like query language (OQL)

yes

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

.Net
All JVM based languages
C++
Groovy
Java
Scala

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

yes

based on PostgreSQL

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication

yes

based on PostgreSQL

Configurable consistency for N replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

yes, on a single node

ACID

ACID for single-table writes

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.

yes

through memory mapped files

User concepts

Access control

Users and groups

LDAP bind authentication

Access rights per client and object definable

yes

based on PostgreSQL

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column based storage and time partitioned...
» more

Competitive advantages

Real-time data ingestion and istant SQL queries for time series High performance...
» more

Typical application scenarios

Application metrics Financial market data and algo trading DevOps monitoring Real-time...
» more

Licensing and pricing models

Apache 2.0.
» more

News

Time Series Forecasting with TensorFlow and QuestDB
20 June 2022

Building a Data Pipeline using QuestDB and Confluent Kafka
7 June 2022

QuestDB 6.4 Release Highlights
31 May 2022

4Bn rows/sec query benchmark: Clickhouse vs QuestDB vs Timescale
26 May 2022

How to build a real-time crypto tracker with Redpanda and QuestDB
25 May 2022

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