DBMS > ArcadeDB vs. Infobright vs. OrigoDB vs. Postgres-XL

System Properties Comparison ArcadeDB vs. Infobright vs. OrigoDB vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

A fully ACID in-memory object graph database

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.02
Rank	#374	Overall
	#52	Document stores
	#38	Graph DBMS
	#56	Key-value stores
	#38	Time Series DBMS

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Website

arcadedb.com

ignitetech.com/softwarelibrary/infobrightdb

origodb.com

www.postgres-xl.org

Technical documentation

docs.arcadedb.com

origodb.com/docs

www.postgres-xl.org/documentation

Developer

Arcade Data

Ignite Technologies Inc.; formerly InfoBright Inc.

Robert Friberg et al

Initial release

2021

2005

2009

under the name LiveDB

2014

since 2012, originally named StormDB

Current release

September 2021

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

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

Open Source

Mozilla public license

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

Server operating systems

All OS with a Java VM

Linux
Windows

Linux
macOS

Data scheme

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

distributed, parallel query execution

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java

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

.Net

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

yes

relationship in graphs

depending on model

yes

Transaction concepts

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

ACID

MVCC

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Role based authorization

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.

Share this page