DBMS > Manticore Search vs. RDF4J vs. Rockset vs. SAP HANA

System Properties Comparison Manticore Search vs. RDF4J vs. Rockset vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

A scalable, reliable search and analytics service in the cloud, built on RocksDB

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Relational DBMS
Search engine

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

manticoresearch.com

rdf4j.org

rockset.com

www.sap.com/products/hana.html

Technical documentation

manual.manticoresearch.com

rdf4j.org/documentation

docs.rockset.com

help.sap.com/hana

Developer

Manticore Software

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

Rockset

SAP

Initial release

2017

2004

2019

2010

Current release

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GPL version 2

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java

C++

Server operating systems

FreeBSD
Linux
macOS
Windows

Linux
OS X
Unix
Windows

hosted

Appliance or cloud-service

Data scheme

Fixed schema

yes

RDF Schemas

schema-free

yes

Typing

predefined data types such as float or date

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

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

full-text index on all search fields

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

Read-only SQL queries, including JOINs

yes

APIs and other access methods

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

HTTP REST

JDBC
ODBC

Supported programming languages

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

Java
PHP
Python

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

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

Access rights for users and organizations can be defined via Rockset console

yes

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.