DBMS > ToroDB vs. YottaDB

System Properties Comparison ToroDB vs. YottaDB

Please select another system to include it in the comparison.

Our visitors often compare ToroDB and YottaDB with MongoDB, SurrealDB and PostgreSQL.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A fast and solid embedded Key-value store

Primary database model

Document store

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	0.23
Rank	#301	Overall
	#44	Key-value stores

Website

github.com/torodb/server

yottadb.com

Technical documentation

yottadb.com/resources/documentation

Developer

8Kdata

YottaDB, LLC

Initial release

2016

2001

License

Commercial or Open Source

Open Source

AGPL-V3

Open Source

AGPL 3.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

Java

Server operating systems

All OS with a Java 7 VM

Docker
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

by using the Octo plugin

APIs and other access methods

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Users and groups based on OS-security mechanisms

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.

Share this page