DBMS > Amazon Neptune vs. Oracle Berkeley DB vs. Percona Server for MongoDB vs. Snowflake

System Properties Comparison Amazon Neptune vs. Oracle Berkeley DB vs. Percona Server for MongoDB vs. Snowflake

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

Widely used in-process key-value store

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Graph DBMS
RDF store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

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	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

aws.amazon.com/neptune

www.oracle.com/database/technologies/related/berkeleydb.html

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

www.snowflake.com

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.oracle.com/cd/E17076_05/html/index.html

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

docs.snowflake.net/manuals/index.html

Developer

Amazon

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Percona

Snowflake Computing Inc.

Initial release

2017

1994

2015

2014

Current release

18.1.40, May 2020

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

GPL Version 2

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, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

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.

Source-replica replication

yes

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

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

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)

Access rights for users and roles

Users with fine-grained authorization concept, user roles and pluggable 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.