DBMS > JaguarDB vs. MongoDB vs. SpatiaLite

System Properties Comparison JaguarDB vs. MongoDB vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Performant, highly scalable DBMS for AI and IoT applications

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

Spatial extension of SQLite

Primary database model

Key-value store

Document store

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

Relational DBMS

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

Score	0.01
Rank	#379	Overall
	#60	Key-value stores

Score	455.18
Rank	#5	Overall
	#1	Document stores

Score	2.23
Rank	#132	Overall
	#3	Spatial DBMS

Website

www.datajaguar.com

www.mongodb.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

www.datajaguar.com/support.php

docs.mongodb.com/manual

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

DataJaguar, Inc.

MongoDB, Inc

Alessandro Furieri

Initial release

2015

2009

2008

Current release

2.9.4 September 2018

6.0.1, August 2022

5.0.0, August 2020

License

Commercial or Open Source

Open Source

GPL V3.0

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

MPL 1.1, GPL v2.0 or LGPL v2.1

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.

ScaleGrid for MongoDB Database: Fully managed hosting for MongoDB Database on a wide variety of cloud providers and On-Premises. Automate your management, scaling and backups through one centralized platform.

Implementation language

C++

the server part. Clients available in other languages

C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

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.

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.

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

Read-only SQL queries via the MongoDB Connector for BI

yes

APIs and other access methods

JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

JavaScript

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.

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

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

yes

User concepts

Access control

rights management via user accounts

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.