DBMS > MongoDB vs. STSdb vs. Typesense

System Properties Comparison MongoDB vs. STSdb vs. Typesense

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Document store

Key-value store

Search engine

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

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

Score	402.51
Rank	#5	Overall
	#1	Document stores

Score	0.03
Rank	#365	Overall
	#57	Key-value stores

Score	0.92
Rank	#192	Overall
	#14	Search engines

Website

www.mongodb.com

github.com/STSSoft/STSdb4

typesense.org

Technical documentation

www.mongodb.com/docs/manual

typesense.org/docs

Developer

MongoDB, Inc

STS Soft SC

Initial release

2009

2011

2015

Current release

7.0.5, January 2024

4.0.8, September 2015

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

GPLv2, commercial license available

Open Source

GPL V3

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

Server operating systems

Linux
OS X
Solaris
Windows

Windows

Linux

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.

yes

schema-free

pre-defined schema optional

Typing

predefined data types such as float or date

yes

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

yes

primitive types and user defined types (classes)

yes

Secondary indexes

yes

SQL

Support of SQL

Read-only SQL queries via the MongoDB Atlas SQL Interface

APIs and other access methods

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

.NET Client API

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

C#
Java

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

JavaScript

Triggers

yes

in MongoDB Atlas only

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 deployments with MongoDB Atlas Global Clusters
Source-replica replication

none

Multi-source replication using RAFT

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

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

Multi-document ACID Transactions with snapshot isolation

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

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.