DBMS > Amazon Neptune vs. Amazon Redshift vs. Percona Server for MongoDB vs. Transbase

System Properties Comparison Amazon Neptune vs. Amazon Redshift vs. Percona Server for MongoDB vs. Transbase

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 drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A resource-optimized, high-performance, universally applicable 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	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/neptune

aws.amazon.com/redshift

www.percona.com/mongodb/software/percona-server-for-mongodb

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

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.aws.amazon.com/redshift

docs.percona.com/percona-distribution-for-mongodb

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

Developer

Amazon

Amazon (based on PostgreSQL)

Percona

Transaction Software GmbH

Initial release

2017

2012

2015

1987

Current release

3.4.10-2.10, November 2017

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

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

C++

C and C++

Server operating systems

hosted

Linux

FreeBSD
Linux
macOS
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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC

proprietary protocol using JSON

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

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

Server-side scripts

Stored procedures

user defined functions

in Python

JavaScript

yes

Triggers

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.

yes

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

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

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

via In-Memory Engine

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

Access rights for users and roles

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.