DBMS > Amazon DocumentDB vs. GeoMesa vs. Netezza vs. Stardog

System Properties Comparison Amazon DocumentDB vs. GeoMesa vs. Netezza vs. Stardog

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Data warehouse and analytics appliance part of IBM PureSystems

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

aws.amazon.com/documentdb

www.geomesa.org

www.ibm.com/products/netezza

www.stardog.com

Technical documentation

aws.amazon.com/documentdb/resources

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

docs.stardog.com

Developer

CCRi and others

IBM

Stardog-Union

Initial release

2019

2014

2000

2010

Current release

5.0.0, May 2024

7.3.0, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Scala

Java

Server operating systems

hosted

Linux

included in appliance

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC
OLE DB

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

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

depending on storage layer

Source-replica replication

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

relationships in graphs

Transaction concepts

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

Atomic single-document operations

ACID

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.

depending on storage layer

yes

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

Access rights for users and roles

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Use LangChain and vector search on Amazon DocumentDB to build a generative AI chatbot | Amazon Web Services
20 May 2024, AWS Blog

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

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

Use headless clusters in Amazon DocumentDB for cost-effective multi-Region resiliency | Amazon Web Services
8 March 2024, AWS Blog

provided by Google News

IBM announces availability of the high-performance, cloud-native Netezza Performance Server as a Service on AWS
11 July 2023, IBM

AWS and IBM Netezza come out in support of Iceberg in table format face-off
1 August 2023, The Register

Migrating your Netezza data warehouse to Amazon Redshift | Amazon Web Services
27 May 2020, AWS Blog

IBM Brings Back a Netezza, Attacks Yellowbrick
29 June 2020, Datanami

Netezza Performance Server
12 August 2020, IBM

provided by Google News

Share this page