DBMS > NSDb vs. OrigoDB vs. WakandaDB vs. Yaacomo

System Properties Comparison NSDb vs. OrigoDB vs. WakandaDB vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Time Series DBMS

Document store
Object oriented DBMS

Object oriented DBMS

Relational DBMS

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

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

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

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

nsdb.io

origodb.com

wakanda.github.io

yaacomo.com

Technical documentation

nsdb.io/Architecture

origodb.com/docs

wakanda.github.io/doc

Developer

Robert Friberg et al

Wakanda SAS

Q2WEB GmbH

Initial release

2017

2009

under the name LiveDB

2012

2009

Current release

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

AGPLv3, extended commercial license available

commercial

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, Scala

C++, JavaScript

Server operating systems

Linux
macOS

Linux
Windows

Linux
OS X
Windows

Android
Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

RESTful HTTP API

JDBC
ODBC

Supported programming languages

Java
Scala

.Net

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

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

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

Using Apache Lucene

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

Role based authorization

yes

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.

Share this page