DBMS > Amazon DocumentDB vs. Cachelot.io vs. Graph Engine vs. Manticore Search

System Properties Comparison Amazon DocumentDB vs. Cachelot.io vs. Graph Engine vs. Manticore Search

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

In-memory caching system

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Primary database model

Document store

Key-value store

Graph DBMS
Key-value store

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	1.91
Rank	#124	Overall
	#22	Document stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.23
Rank	#301	Overall
	#21	Search engines

Website

aws.amazon.com/documentdb

cachelot.io

www.graphengine.io

manticoresearch.com

Technical documentation

aws.amazon.com/documentdb/resources

www.graphengine.io/docs/manual

manual.manticoresearch.com

Developer

Microsoft

Manticore Software

Initial release

2019

2015

2010

2017

Current release

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Simplified BSD License

Open Source

MIT License

Open Source

GPL version 2

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

C++

.NET and C

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

.NET

FreeBSD
Linux
macOS
Windows

Data scheme

schema-free

yes

Fixed schema

Typing

predefined data types such as float or date

yes

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

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

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Memcached protocol

RESTful HTTP API

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

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

none

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

Atomic single-document operations

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

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

In-memory capabilities

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Unlock the power of parallel indexing in Amazon DocumentDB
19 June 2024, AWS Blog

AWS announces Amazon DocumentDB zero-ETL integration with Amazon OpenSearch Service
16 May 2024, AWS Blog

Reduce cost and improve performance by migrating to Amazon DocumentDB 5.0
15 April 2024, AWS Blog

Update your Amazon DocumentDB TLS certificates: Expiring in 2024
28 March 2024, AWS Blog

Unlock the power of Amazon DocumentDB text search with real-world use cases
5 March 2024, AWS Blog

provided by Google News

Trinity
30 October 2010, microsoft.com

Open source Microsoft Graph Engine takes on Neo4j
13 February 2017, InfoWorld

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

The graph analytics landscape 2019
27 February 2019, Data Science Central

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

provided by Google News

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, hackernoon.com

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Highlighting in Search Results
24 May 2020, hackernoon.com

40 Stories To Learn About Elasticsearch
27 April 2023, hackernoon.com

provided by Google News

Share this page