DBMS > Graphite vs. Manticore Search vs. Microsoft Azure Cosmos DB vs. PostGIS

System Properties Comparison Graphite vs. Manticore Search vs. Microsoft Azure Cosmos DB vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Multi-storage database for search, including full-text search.

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

Primary database model

Time Series DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

Relational DBMS

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

github.com/graphite-project/graphite-web

manticoresearch.com

azure.microsoft.com/services/cosmos-db

postgis.net

Technical documentation

graphite.readthedocs.io

manual.manticoresearch.com

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

Developer

Chris Davis

Manticore Software

Microsoft

Initial release

2006

2017

2014

2005

Current release

6.0, February 2023

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2

commercial

Open Source

GPL v2.0

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

Python

C++

Server operating systems

Linux
Unix

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

yes

Fixed schema

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

JSON types

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

HTTP API
Sockets

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

JavaScript (Node.js)
Python

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

user defined functions

JavaScript

user defined functions

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

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

User concepts

Access control

Access rights can be defined down to the item level

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.