DBMS > Amazon Neptune vs. Geode vs. Qdrant vs. SQLite

System Properties Comparison Amazon Neptune vs. Geode vs. Qdrant vs. SQLite

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Widely used embeddable, in-process RDBMS

Primary database model

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.86
Rank	#134	Overall
	#24	Key-value stores

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/neptune

geode.apache.org

github.com/qdrant/qdrant
qdrant.tech

www.sqlite.org

Technical documentation

aws.amazon.com/neptune/developer-resources

geode.apache.org/docs

qdrant.tech/documentation

www.sqlite.org/docs.html

Developer

Amazon

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Qdrant

Dwayne Richard Hipp

Initial release

2017

2002

2021

2000

Current release

1.1, February 2017

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2.0

Open Source

Public Domain

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

Rust

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

Docker
Linux
macOS
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

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.

Multi-source replication

Collection-level replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency, tunable 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, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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)

Access rights per client and object definable

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.