DBMS > Graph Engine vs. Manticore Search vs. NebulaGraph

System Properties Comparison Graph Engine vs. Manticore Search vs. NebulaGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

A distributed, linear scalable, high perfomant Graph DBMS

Primary database model

Graph DBMS
Key-value store

Search engine

Graph DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.52
Rank	#243	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.26
Rank	#291	Overall
	#21	Search engines

Score	1.61
Rank	#136	Overall
	#11	Graph DBMS

Website

www.graphengine.io

manticoresearch.com

github.com/vesoft-inc/nebula
www.nebula-graph.io

Technical documentation

www.graphengine.io/docs/manual

manual.manticoresearch.com

docs.nebula-graph.io

Developer

Microsoft

Manticore Software

Vesoft Inc.

Initial release

2010

2017

2019

Current release

6.0, February 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2

Open Source

Apache Version 2.0 + Common Clause 1.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

C++

Server operating systems

.NET

FreeBSD
Linux
macOS
Windows

Linux

Data scheme

yes

Fixed schema

Strong typed schema

Typing

predefined data types such as float or date

yes

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

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

Secondary indexes

yes

full-text index on all search fields

yes

Nebula Graph internally uses the Key-Value store RocksDB for persistency. The vertices, edges, and their properties are stored as Key while their values are stored as Value. The primary indexes are per Key and secondary indexes are per Value.

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

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

Browser interface
console (shell)
Cypher Query Language
GO Object Graph Mapper
Java Object Graph Mapper
NGBatis

ORM framework for NebulaGraph and Spring-Boot
Proprietary native API
Python Object Graph Mapper
Query language nGQL

Supported programming languages

C#
C++
F#
Visual Basic

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

.Net
C++
Go
Java
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

Causal Clustering using Raft protocol

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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.

yes

using RocksDB

In-memory capabilities

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

yes

User concepts

Access control

Role-based access control

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

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

Microsoft Demos New Office 365 and SharePoint Online Collaboration Technologies
3 March 2014, Redmondmag.com

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

thatDot launches Quine, a streaming graph engine
23 February 2022, TechCrunch

Hey, corporate types. Microsoft would really love to pick your brains about Project Cortex
5 November 2019, theregister.com

provided by Google News

Manticore is on search for new investment and partners
9 December 2024, Blocks and Files

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, HackerNoon

Manticore Search Now Integrates With Grafana
9 August 2023, HackerNoon

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, HackerNoon

Integrating Manticore Search with Apache Superset
8 August 2023, HackerNoon

provided by Google News

NebulaGraph reaps from China’s growing appetite for graph databases
16 September 2022, TechCrunch

LlamaIndex Unveils Notebook Implementation of GraphRAG
17 July 2024, Analytics India Magazine

Nebula Graph an open source graph-oriented DBMS
30 January 2021, Desde Linux

provided by Google News

Share this page