DBMS > BigObject vs. OrientDB vs. Sequoiadb vs. Trafodion

System Properties Comparison BigObject vs. OrientDB vs. Sequoiadb vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Analytic DBMS for real-time computations and queries

Multi-model DBMS (Document, Graph, Key/Value)

NewSQL database with distributed OLTP and SQL

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store
Graph DBMS
Key-value store

Document store
Relational DBMS

Relational DBMS

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Website

Technical documentation

docs.bigobject.io

www.orientdb.com/docs/last/index.html

www.sequoiadb.com/en/index.php?m=Files&a=index

trafodion.apache.org/documentation.html

Developer

BigObject, Inc.

OrientDB LTD; CallidusCloud; SAP

Sequoiadb Ltd.

Apache Software Foundation, originally developed by HP

Initial release

2015

2010

2013

2014

Current release

3.2.29, March 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache version 2

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache 2.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

C++

C++, 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)

All OS with a Java JDK (>= JDK 6)

Linux

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language, no joins

SQL-like query language

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

proprietary protocol using JSON

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C++
Java
PHP
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Lua

Java, Javascript

JavaScript

Java Stored Procedures

Triggers

Hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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; record level security configurable

simple password-based access control

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.

More resources

DB-Engines blog posts

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, Matthias Gelbmann

show all

Recent citations in the news

OrientDB: A Flexible and Scalable Multi-Model NoSQL DBMS
21 January 2022, Open Source For You

Comparing Graph Databases II. Part 2: ArangoDB, OrientDB, and… | by Sam Bell
20 September 2019, Towards Data Science

The 12 Best Graph Databases to Consider for 2024
22 October 2023, Solutions Review

ArangoDB raises $10 million for NoSQL database management
14 March 2019, VentureBeat

HNS IoT Botnet Evolves, Goes Cross-Platform
10 July 2018, Dark Reading

provided by Google News

SQL-on-Hadoop Database Trafodion Bridges Transactions and Analysis
24 January 2018, The New Stack

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

Low-latency, distributed database architectures are critical for emerging fog applications
16 July 2022, Embedded Computing Design

provided by Google News

Share this page