DBMS > Newts vs. RDF4J vs. SAP HANA vs. Sphinx vs. Teradata Aster

System Properties Comparison Newts vs. RDF4J vs. SAP HANA vs. Sphinx vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Time Series DBMS based on Cassandra

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

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

Open source search engine for searching in data from different sources, e.g. relational databases

Platform for big data analytics on multistructured data sources and types

Primary database model

Secondary database models

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.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

opennms.github.io/newts

rdf4j.org

www.sap.com/products/hana.html

sphinxsearch.com

Technical documentation

github.com/OpenNMS/newts/wiki

rdf4j.org/documentation

help.sap.com/hana

sphinxsearch.com/docs

Developer

OpenNMS Group

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

SAP

Sphinx Technologies Inc.

Teradata

Initial release

2014

2004

2010

2001

2005

Current release

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

GPL version 2, commercial licence available

commercial

Cloud-based only

Only available as a cloud service

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

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

RDF Schemas

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

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.

yes

in Aster File Store

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

HTTP REST
Java API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

Proprietary protocol

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Java

Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

SQLScript, R

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

yes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

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

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

yes

fine grained access rights according to SQL-standard

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.