DBMS > 4D vs. CockroachDB vs. Geode vs. GeoMesa

System Properties Comparison 4D vs. CockroachDB vs. Geode vs. GeoMesa

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

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

Primary database model

Relational DBMS

Key-value store

Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Website

www.4d.com

www.cockroachlabs.com

geode.apache.org

www.geomesa.org

Technical documentation

developer.4d.com

www.cockroachlabs.com/docs

geode.apache.org/docs

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

Developer

4D, Inc

Cockroach Labs

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

CCRi and others

Initial release

1984

2015

2002

2014

Current release

v20, April 2023

23.1.1, May 2023

1.1, February 2017

4.0.5, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache License 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

Scala

Server operating systems

OS X
Windows

Linux
macOS
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

yes

dynamic schema

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, wire compatible with PostgreSQL

SQL-like query language (OQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

4D proprietary IDE
PHP

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

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

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using RAFT

Multi-source replication

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

depending on storage layer

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

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

depending on storage layer

User concepts

Access control

Users and groups

Role-based access control

Access rights per client and object definable

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

Cockroach Labs Deepens Partnership with Google Cloud, CockroachDB Selected to Join Google Distributed Cloud
9 April 2024, PR Newswire

DoorDash Uses CockroachDB to Create Config Management Platform for Microservices
14 February 2024, InfoQ.com

How to Unlock Real-Time Data Streams with CockroachDB and Amazon MSK | Amazon Web Services
6 November 2023, AWS Blog

CockroachDB tempts legacy databases to crawl into the cloud age
29 January 2024, The Register

How DoorDash Migrated from Aurora Postgres to CockroachDB
5 December 2023, The New Stack

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page