DBMS > OrigoDB vs. Snowflake vs. Sphinx vs. VelocityDB vs. Warp 10

System Properties Comparison OrigoDB vs. Snowflake vs. Sphinx vs. VelocityDB vs. Warp 10

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

Open source search engine for searching in data from different sources, e.g. relational databases

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Object oriented DBMS

Relational DBMS

Search engine

Graph DBMS
Object oriented DBMS

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	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

Technical documentation

origodb.com/docs

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

velocitydb.com/UserGuide

www.warp10.io/content/02_Getting_started

Developer

Robert Friberg et al

Snowflake Computing Inc.

Sphinx Technologies Inc.

VelocityDB Inc

SenX

Initial release

2009

under the name LiveDB

2014

2001

2011

2015

Current release

3.5.1, February 2023

7.x

License

Commercial or Open Source

Open Source

commercial

Open Source

GPL version 2, commercial licence available

commercial

Open Source

Apache License 2.0

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

Java

Server operating systems

Linux
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Any that supports .NET

Linux
OS X
Windows

Data scheme

yes

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

yes

schema-free

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Proprietary protocol

.Net

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

.Net

Server-side scripts

Stored procedures

yes

user defined functions

yes

WarpScript

Triggers

yes

Domain Events

similar concept for controling cloud resources

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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

The original contents of fields are not stored in the Sphinx index.

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

Based on Windows Authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.