DBMS > Amazon Neptune vs. FatDB vs. IBM Cloudant vs. XTDB

System Properties Comparison Amazon Neptune vs. FatDB vs. IBM Cloudant vs. XTDB

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.

Description

Fast, reliable graph database built for the cloud

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

Database as a Service offering based on Apache CouchDB

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Document store

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	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

aws.amazon.com/neptune

www.ibm.com/products/cloudant

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

aws.amazon.com/neptune/developer-resources

cloud.ibm.com/docs/Cloudant

www.xtdb.com/docs

Developer

Amazon

FatCloud

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Juxt Ltd.

Initial release

2017

2012

2010

2019

Current release

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

MIT License

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

Erlang

Clojure

Server operating systems

hosted

Windows

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

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

RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

Clojure
Java

Server-side scripts

Stored procedures

yes

via applications

View functions (Map-Reduce) in JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

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

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

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

Access rights for users can be defined per database

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

Recent citations in the news

Exploring new features of Apache TinkerPop 3.7.x in Amazon Neptune | Amazon Web Services
7 June 2024, AWS Blog

Building NHM London's Planetary Knowledge Base with Amazon Neptune and the Registry of Open Data on AWS ...
5 June 2024, AWS Blog

Unit testing Apache TinkerPop transactions: From TinkerGraph to Amazon Neptune | Amazon Web Services
3 June 2024, AWS Blog

AWS announces Amazon Neptune I/O-Optimized
22 February 2024, AWS Blog

Amazon Neptune Analytics is now available in the AWS Europe (London) Region
14 March 2024, AWS Blog

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, ibm.com

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, ibm.com

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

Share this page