DBMS > DataFS vs. EsgynDB vs. Percona Server for MongoDB vs. VoltDB

System Properties Comparison DataFS vs. EsgynDB vs. Percona Server for MongoDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Graph DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

newdatabase.com

www.esgyn.cn

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

www.voltdb.com

Technical documentation

dev.mobiland.com/Overview.xsp

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

docs.voltdb.com

Developer

Mobiland AG

Esgyn

Percona

VoltDB Inc.

Initial release

2018

2015

2010

Current release

1.1.263, October 2022

3.4.10-2.10, November 2017

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java

C++

Java, C++

Server operating systems

Windows

Linux

Linux
OS X

for development

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C
C#
C++
VB.Net

All languages supporting JDBC/ODBC/ADO.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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

Java

Triggers

no, except callback-events from server when changes happened

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

Multi-source replication
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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Windows-Profile

fine grained access rights according to SQL-standard

Access rights for users and roles

Users and roles with access to stored procedures

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

Recent citations in the news

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

How to Plan Your MongoDB Upgrade
29 January 2024, The New Stack

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

6 keys to MongoDB database security
22 May 2019, InfoWorld

DB or not DB: Open-sourcer Percona pushes out plethora of SQL and NoSQL tweaks in bid to win over suits
19 May 2020, The Register

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page