DBMS > Amazon Neptune vs. Amazon Redshift vs. Couchbase vs. OpenEdge

System Properties Comparison Amazon Neptune vs. Amazon Redshift vs. Couchbase vs. OpenEdge

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

Large scale data warehouse service for use with business intelligence tools

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

Application development environment with integrated database management system

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.20
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Website

aws.amazon.com/neptune

aws.amazon.com/redshift

www.couchbase.com

www.progress.com/openedge

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.aws.amazon.com/redshift

docs.couchbase.com

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Amazon

Amazon (based on PostgreSQL)

Couchbase, Inc.

Progress Software Corporation

Initial release

2017

2012

2011

1984

Current release

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

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

Open Source

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

commercial

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

C, C++, Go and Erlang

Server operating systems

hosted

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

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

yes

close to SQL 92

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC

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

JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

user defined functions

in Python

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

yes

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic Sharding

horizontal partitioning

since Version 11.4

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.

yes

Multi-source replication

including cross data center replication
Source-replica 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

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

informational only, not enforced by the system

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.

yes

Ephemeral buckets

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.

Users and groups

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.