DBMS > AlaSQL vs. OrientDB vs. OrigoDB vs. Sadas Engine

System Properties Comparison AlaSQL vs. OrientDB vs. OrigoDB vs. Sadas Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

A fully ACID in-memory object graph database

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Document store
Relational DBMS

Document store
Graph DBMS
Key-value store

Document store
Object oriented DBMS

Relational DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

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

origodb.com/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Andrey Gershun & Mathias R. Wulff

OrientDB LTD; CallidusCloud; SAP

Robert Friberg et al

SADAS s.r.l.

Initial release

2014

2010

2009

under the name LiveDB

2006

Current release

3.2.29, March 2024

8.0

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache version 2

Open Source

commercial

free trial version available

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

JavaScript

Java

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

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

Linux
Windows

AIX
Linux
Windows

Data scheme

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

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

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language, no joins

yes

APIs and other access methods

JavaScript API

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

.NET Client API
HTTP API
LINQ

JDBC
ODBC
Proprietary protocol

Supported programming languages

JavaScript

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

.Net

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

Java, Javascript

yes

Triggers

yes

Hooks

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

managed by 'Learn by Usage'

User concepts

Access control

Access rights for users and roles; record level security configurable

Role based authorization

Access rights for users, groups and roles 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

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google 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

Introducing Gremlin The Graph Database
14 August 2013, iProgrammer

provided by Google News

Share this page