DBMS > Amazon Neptune vs. Apache Doris vs. Couchbase vs. Qdrant

System Properties Comparison Amazon Neptune vs. Apache Doris vs. Couchbase vs. Qdrant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

An MPP-based analytics DBMS embracing the MySQL protocol

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector 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	0.60
Rank	#247	Overall
	#113	Relational DBMS

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

aws.amazon.com/neptune

doris.apache.org
github.com/apache/doris

www.couchbase.com

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

aws.amazon.com/neptune/developer-resources

github.com/apache/doris/wiki

docs.couchbase.com

qdrant.tech/documentation

Developer

Amazon

Apache Software Foundation, originally contributed from Baidu

Couchbase, Inc.

Qdrant

Initial release

2017

2011

2021

Current release

1.2.2, February 2023

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache Version 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

Java

C, C++, Go and Erlang

Rust

Server operating systems

hosted

Linux

Linux
OS X
Windows

Docker
Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

SQL

Support of SQL

yes

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
MySQL client

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

Java

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

user defined functions

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Automatic Sharding

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.

none

Multi-source replication

including cross data center replication
Source-replica replication

Collection-level 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

selectable on a per-operation basis

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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.

yes

Ephemeral buckets

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Key-based authentication

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.