DBMS > Infobright vs. Machbase Neo vs. OrientDB vs. Trafodion

System Properties Comparison Infobright vs. Machbase Neo vs. OrientDB 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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

TimeSeries DBMS for AIoT and BigData

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Website

ignitetech.com/softwarelibrary/infobrightdb

machbase.com

orientdb.org

trafodion.apache.org

Technical documentation

machbase.com/dbms

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

trafodion.apache.org/documentation.html

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Machbase

OrientDB LTD; CallidusCloud; SAP

Apache Software Foundation, originally developed by HP

Initial release

2005

2013

2010

2014

Current release

V8.0, August 2023

3.2.29, March 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

free test version available

Open Source

Apache version 2

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

Server operating systems

Linux
Windows

Linux
macOS
Windows

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")

yes

Typing

predefined data types such as float or date

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language, no joins

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

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

Source-replica replication

selectable replication factor

Multi-source 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

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

simple password-based access control

Access rights for users and roles; record level security configurable

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

“Luxembourg is a perfect target area”: Korean accelerator exec
27 October 2022, Delano.lu

provided by Google News

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

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

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

K2View updates DataOps platform with data fabric automation
11 May 2021, TechTarget

provided by Google News

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

HP Throws Trafodion Hat into OLTP Hadoop Ring
14 July 2014, Datanami

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

provided by Google News

Share this page