DBMS > Amazon Neptune vs. FatDB vs. GeoMesa vs. Trafodion

System Properties Comparison Amazon Neptune vs. FatDB vs. GeoMesa vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Fast, reliable graph database built for the cloud

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Transactional SQL-on-Hadoop DBMS

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Spatial DBMS

Relational DBMS

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

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Website

aws.amazon.com/neptune

www.geomesa.org

trafodion.apache.org

Technical documentation

aws.amazon.com/neptune/developer-resources

www.geomesa.org/documentation/stable/user/index.html

trafodion.apache.org/documentation.html

Developer

Amazon

FatCloud

CCRi and others

Apache Software Foundation, originally developed by HP

Initial release

2017

2012

2014

Current release

5.0.1, July 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

Scala

C++, Java

Server operating systems

hosted

Windows

Linux

Data scheme

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

via applications

Java Stored Procedures

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

depending on storage layer

Sharding

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.

selectable replication factor

depending on storage layer

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on storage layer

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

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.

depending on storage layer

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

How Amazon stores deliver trustworthy shopping and seller experiences using Amazon Neptune
18 September 2024, AWS Blog

How Prisma Cloud built Infinity Graph using Amazon Neptune and Amazon OpenSearch Service
27 August 2024, AWS Blog

Hydrating the Natural History Museum’s Planetary Knowledge Base with Amazon Neptune and Open Data on AWS
13 September 2024, AWS Blog

Using knowledge graphs to build GraphRAG applications with Amazon Bedrock and Amazon Neptune
1 August 2024, AWS Blog

New Amazon Neptune engine version delivers up to 9 times faster and 10 times higher throughput for openCypher query performance
23 July 2024, AWS Blog

provided by Google News

Share this page