DBMS > OrigoDB vs. Percona Server for MongoDB vs. VoltDB vs. YTsaurus

System Properties Comparison OrigoDB vs. Percona Server for MongoDB vs. VoltDB vs. YTsaurus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

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

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Document store
Object oriented DBMS

Document store

Relational DBMS

Document store
Key-value store

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Score	0.21
Rank	#324	Overall
	#45	Document stores
	#48	Key-value stores

Website

origodb.com

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

www.voltdb.com

ytsaurus.tech

Technical documentation

origodb.com/docs

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

docs.voltdb.com

ytsaurus.tech/docs/en

Developer

Robert Friberg et al

Percona

VoltDB Inc.

Yandex

Initial release

2009

under the name LiveDB

2015

2010

2023

Current release

3.4.10-2.10, November 2017

11.3, April 2022

License

Commercial or Open Source

Open Source

GPL Version 2

Open Source

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

Open Source

Apache License, Version 2.0

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

C++

Server operating systems

Linux
Windows

Linux

Linux
OS X

for development

Ubuntu

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

only a subset of SQL 99

YQL, an SQL-based language, is supported

APIs and other access methods

.NET Client API
HTTP API
LINQ

proprietary protocol using JSON

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.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

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

JavaScript

Java

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

Snapshots and command logging

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

Role based authorization

Access rights for users and roles

Users and roles with access to stored procedures

Access Control Lists

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

MongoDB Performance Tuning
23 May 2024, Database Trends and Applications

There are lots of ways to put a database in the cloud – here's what to consider
15 September 2023, The Register

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

The Case Against the Server Side Public License (SSPL)
11 October 2022, The New Stack

The essential guide to MongoDB security
2 February 2017, InfoWorld

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