DBMS > BigObject vs. OrigoDB vs. Snowflake vs. Titan

System Properties Comparison BigObject vs. OrigoDB vs. Snowflake vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Analytic DBMS for real-time computations and queries

A fully ACID in-memory object graph database

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store
Object oriented DBMS

Relational DBMS

Graph DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

bigobject.io

origodb.com

www.snowflake.com

github.com/thinkaurelius/titan

Technical documentation

docs.bigobject.io

origodb.com/docs

docs.snowflake.net/manuals/index.html

github.com/thinkaurelius/titan/wiki

Developer

BigObject, Inc.

Robert Friberg et al

Snowflake Computing Inc.

Aurelius, owned by DataStax

Initial release

2015

2009

under the name LiveDB

2014

2012

License

Commercial or Open Source

commercial

free community edition available

Open Source

commercial

Open Source

Apache license, version 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

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
Windows

hosted

Linux
OS X
Unix
Windows

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

yes

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

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net

JavaScript (Node.js)
Python

Clojure
Java
Python

Server-side scripts

Stored procedures

Lua

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

none

horizontal partitioning

client side managed; servers are not synchronized

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

depending on model

yes

Relationships in graph

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

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.