DBMS > OrigoDB vs. Snowflake vs. SWC-DB vs. WakandaDB

System Properties Comparison OrigoDB vs. Snowflake vs. SWC-DB vs. WakandaDB

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

Cloud-based data warehousing service for structured and semi-structured data

A high performance, scalable Wide Column DBMS

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

Primary database model

Document store
Object oriented DBMS

Relational DBMS

Wide column store

Object oriented DBMS

Secondary database models

Time Series DBMS

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	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

origodb.com

www.snowflake.com

github.com/kashirin-alex/swc-db
www.swcdb.org

wakanda.github.io

Technical documentation

origodb.com/docs

docs.snowflake.net/manuals/index.html

wakanda.github.io/doc

Developer

Robert Friberg et al

Snowflake Computing Inc.

Alex Kashirin

Wakanda SAS

Initial release

2009

under the name LiveDB

2014

2020

2012

Current release

0.5, April 2021

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

commercial

Open Source

GPL V3

Open Source

AGPLv3, extended commercial license available

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

C++

C++, JavaScript

Server operating systems

Linux
Windows

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

RESTful HTTP API

Supported programming languages

.Net

JavaScript (Node.js)
Python

C++

JavaScript

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

Domain Events

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

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.