DBMS > Amazon DynamoDB vs. HugeGraph vs. OrigoDB vs. Percona Server for MongoDB

System Properties Comparison Amazon DynamoDB vs. HugeGraph vs. OrigoDB vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A fast-speed and highly-scalable Graph DBMS

A fully ACID in-memory object graph database

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

Primary database model

Document store
Key-value store

Graph DBMS

Document store
Object oriented DBMS

Document store

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

aws.amazon.com/dynamodb

github.com/hugegraph
hugegraph.apache.org

origodb.com

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

Technical documentation

docs.aws.amazon.com/dynamodb

hugegraph.apache.org/docs

origodb.com/docs

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

Developer

Amazon

Baidu

Robert Friberg et al

Percona

Initial release

2012

2018

2009

under the name LiveDB

2015

Current release

0.9

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

GPL Version 2

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

Java

C++

Server operating systems

hosted

Linux
macOS
Unix

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

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

also supports composite index and range index

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP API
TinkerPop Gremlin

.NET Client API
HTTP API
LINQ

proprietary protocol using JSON

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Groovy
Java
Python

.Net

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

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

yes

JavaScript

Triggers

yes

by integration with AWS Lambda

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

via hugegraph-spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

depending on model

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

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)

Users, roles and permissions

Role based authorization

Access rights for 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.