DBMS > Amazon DocumentDB vs. Geode vs. Postgres-XL vs. Yanza

System Properties Comparison Amazon DocumentDB vs. Geode vs. Postgres-XL vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	1.89
Rank	#137	Overall
	#24	Document stores

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/documentdb

geode.apache.org

www.postgres-xl.org

yanza.com

Technical documentation

aws.amazon.com/documentdb/resources

geode.apache.org/docs

www.postgres-xl.org/documentation

Developer

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

Yanza

Initial release

2019

2002

2014

since 2012, originally named StormDB

2015

Current release

1.1, February 2017

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Mozilla public license

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS

Windows

Data scheme

schema-free

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

distributed, parallel query execution

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

yes, on a single node

ACID

MVCC

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

User concepts

Access control

Access rights for users and roles

Access rights per client and object definable

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

Recent citations in the news

Vector search for Amazon DocumentDB (with MongoDB compatibility) is now generally available | Amazon Web Services
29 November 2023, AWS Blog

AWS announces Amazon DocumentDB I/O-Optimized
21 November 2023, AWS Blog

Reduce cost and improve performance by migrating to Amazon DocumentDB 5.0 | Amazon Web Services
15 April 2024, AWS Blog

AWS announces vector search for Amazon DocumentDB
29 November 2023, AWS Blog

Mask sensitive Amazon DocumentDB log data with Amazon CloudWatch Logs data protection | Amazon Web Services
16 April 2024, AWS Blog

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

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

RDBMS and Apache Geode Data Movement: Low Latency ETL Pipeline by Using Cloud-Native Event Driven ...
30 June 2018, InfoQ.com

provided by Google News

Share this page