DBMS > Dgraph vs. EXASOL vs. Manticore Search vs. RDF4J vs. Snowflake

System Properties Comparison Dgraph vs. EXASOL vs. Manticore Search vs. RDF4J vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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.48
Rank	#158	Overall
	#15	Graph DBMS

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	0.23
Rank	#317	Overall
	#21	Search engines

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

dgraph.io/docs

www.exasol.com/resources

manual.manticoresearch.com

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Dgraph Labs, Inc.

Exasol

Manticore Software

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Initial release

2016

2000

2017

2004

2014

Current release

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL version 2

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

Linux
OS X
Unix
Windows

hosted

Data scheme

schema-free

yes

Fixed schema

yes

RDF Schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

.Net
JDBC
ODBC
WebSocket

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

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

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

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

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Synchronous replication based on Galera library

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.