DBMS > Amazon Neptune vs. FatDB vs. Qdrant vs. Transbase

System Properties Comparison Amazon Neptune vs. FatDB vs. Qdrant vs. Transbase

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.

A high-performance vector database with neural network or semantic-based matching

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Vector DBMS

Relational 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	1.28
Rank	#167	Overall
	#8	Vector DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/neptune

github.com/qdrant/qdrant
qdrant.tech

www.transaction.de/en/products/transbase.html

Technical documentation

aws.amazon.com/neptune/developer-resources

qdrant.tech/documentation

www.transaction.de/en/products/transbase/features.html

Developer

Amazon

FatCloud

Qdrant

Transaction Software GmbH

Initial release

2017

2012

2021

1987

Current release

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

free development 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

Rust

C and C++

Server operating systems

hosted

Windows

Docker
Linux
macOS
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Collection-level replication

Source-replica replication

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, tunable consistency

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

yes

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)

Can implement custom security layer via applications

Key-based authentication

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

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

Open source vector database startup Qdrant raises $28M
23 January 2024, TechCrunch

Qdrant Raises $28M to Advance Massive-Scale AI Applications
23 January 2024, businesswire.com

Qdrant Hybrid Cloud is Now Available for OCI Customers: Managed Vector Search Engine for Data-Sensitive AI ...
16 April 2024, blogs.oracle.com

Qdrant offers managed vector database for hybrid clouds
16 April 2024, InfoWorld

Why Vector Data Services For AI Are A Moveable Feast
17 April 2024, Forbes

provided by Google News

Share this page