DBMS > Geode vs. Microsoft Azure Cosmos DB vs. OrigoDB vs. PostGIS

System Properties Comparison Geode vs. Microsoft Azure Cosmos DB vs. OrigoDB vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

A fully ACID in-memory object graph database

Spatial extension of PostgreSQL

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Object oriented DBMS

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

geode.apache.org

azure.microsoft.com/services/cosmos-db

origodb.com

postgis.net

Technical documentation

geode.apache.org/docs

learn.microsoft.com/azure/cosmos-db

origodb.com/docs

postgis.net/documentation

Developer

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

Microsoft

Robert Friberg et al

Initial release

2002

2014

2009

under the name LiveDB

2005

Current release

1.1, February 2017

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPL v2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API
HTTP API
LINQ

Supported programming languages

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

user defined functions

Triggers

yes

Cache Event Listeners

JavaScript

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

yes, on a single node

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights per client and object definable

Access rights can be defined down to the item level

Role based authorization

yes

based on PostgreSQL

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.