DBMS > MongoDB vs. Newts vs. PostGIS

System Properties Comparison MongoDB vs. Newts vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

Time Series DBMS based on Cassandra

Spatial extension of PostgreSQL

Primary database model

Document store

Time Series DBMS

Spatial DBMS

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

Relational DBMS

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

Score	402.51
Rank	#5	Overall
	#1	Document stores

Score	0.00
Rank	#385	Overall
	#42	Time Series DBMS

Score	18.94
Rank	#30	Overall
	#1	Spatial DBMS

Website

www.mongodb.com

opennms.github.io/newts

postgis.net

Technical documentation

www.mongodb.com/docs/manual

github.com/OpenNMS/newts/wiki

postgis.net/documentation

Developer

MongoDB, Inc

OpenNMS Group

Initial release

2009

2014

2005

Current release

7.0.5, January 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

Open Source

Apache 2.0

Open Source

GPL v2.0

Cloud-based only

Only available as a cloud service

MongoDB available as DBaaS (MongoDB Atlas)

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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

Read-only SQL queries via the MongoDB Atlas SQL Interface

yes

APIs and other access methods

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

HTTP REST
Java API

Supported programming languages

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Java

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

yes

in MongoDB Atlas only

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

Sharding

based on Cassandra

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

Multi-document ACID Transactions with snapshot isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional, enabled by default

yes

In-memory capabilities

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

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

Access rights for users and roles

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.