DBMS > Amazon Neptune vs. Drizzle vs. OrigoDB vs. Trafodion

System Properties Comparison Amazon Neptune vs. Drizzle vs. OrigoDB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Fast, reliable graph database built for the cloud

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A fully ACID in-memory object graph database

Transactional SQL-on-Hadoop DBMS

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

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.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

aws.amazon.com/neptune

origodb.com

trafodion.apache.org

Technical documentation

aws.amazon.com/neptune/developer-resources

origodb.com/docs

trafodion.apache.org/documentation.html

Developer

Amazon

Drizzle project, originally started by Brian Aker

Robert Friberg et al

Apache Software Foundation, originally developed by HP

Initial release

2017

2008

2009

under the name LiveDB

2014

Current release

7.2.4, September 2012

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache 2.0

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++, Java

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C
C++
Java
PHP

.Net

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Triggers

hooks for callbacks inside the server can be used.

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

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.

Multi-source replication
Source-replica replication

Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

depending on model

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

Write ahead log

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)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Find and link similar entities in a knowledge graph using Amazon Neptune, Part 1: Full-text search | Amazon Web ...
7 May 2024, AWS Blog

Find and link similar entities in a knowledge graph using Amazon Neptune, Part 2: Vector similarity search | Amazon ...
7 May 2024, AWS Blog

AWS announces Amazon Neptune I/O-Optimized
22 February 2024, AWS Blog

Amazon Neptune Analytics is now available in the AWS Europe (London) Region
14 March 2024, AWS Blog

Analyze large amounts of graph data to get insights and find trends with Amazon Neptune Analytics | Amazon Web ...
29 November 2023, AWS Blog

provided by Google News

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

HP Throws Trafodion Hat into OLTP Hadoop Ring
14 July 2014, Datanami

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page