DBMS > Amazon Neptune vs. LeanXcale vs. Oracle Berkeley DB vs. Snowflake vs. Tarantool

System Properties Comparison Amazon Neptune vs. LeanXcale vs. Oracle Berkeley DB vs. Snowflake vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Widely used in-process key-value store

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Graph DBMS
RDF store

Key-value store
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

aws.amazon.com/neptune

www.leanxcale.com

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

www.snowflake.com

www.tarantool.io

Technical documentation

aws.amazon.com/neptune/developer-resources

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

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

Developer

Amazon

LeanXcale

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Initial release

2017

2015

1994

2014

2008

Current release

18.1.40, May 2020

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

commercial license available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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 and C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

BSD
Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

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

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

through Apache Derby

yes

SQL interfaced based on SQLite is available

yes

Full-featured ANSI SQL support

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

CLI Client
JDBC
ODBC

Open binary protocol

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C
Java
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

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

only for the SQL API

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

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

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.