DBMS > Amazon Neptune vs. Atos Standard Common Repository vs. PostGIS vs. SAP HANA vs. TempoIQ

System Properties Comparison Amazon Neptune vs. Atos Standard Common Repository vs. PostGIS vs. SAP HANA vs. TempoIQ

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Fast, reliable graph database built for the cloud

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Spatial extension of PostgreSQL

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Spatial DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

aws.amazon.com/neptune

atos.net/en/convergence-creators/portfolio/standard-common-repository

postgis.net

www.sap.com/products/hana.html

tempoiq.com (offline)

Technical documentation

aws.amazon.com/neptune/developer-resources

postgis.net/documentation

help.sap.com/hana

Developer

Amazon

Atos Convergence Creators

SAP

TempoIQ

Initial release

2017

2016

2005

2010

2012

Current release

1703

3.4.2, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

Linux

Appliance or cloud-service

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

LDAP

JDBC
ODBC

HTTP API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages with LDAP bindings

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

yes

based on PostgreSQL

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

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 roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

yes

based on PostgreSQL

yes

simple authentication-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.