DBMS > AlaSQL vs. Dgraph vs. MySQL vs. OrigoDB vs. Ultipa

System Properties Comparison AlaSQL vs. Dgraph vs. MySQL vs. OrigoDB vs. Ultipa

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Distributed and scalable native Graph DBMS

Widely used open source RDBMS

A fully ACID in-memory object graph database

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Document store
Relational DBMS

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	1.39
Rank	#155	Overall
	#15	Graph DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

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

Score	0.11
Rank	#338	Overall
	#32	Graph DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

dgraph.io/docs

dev.mysql.com/doc

origodb.com/docs

www.ultipa.com/document

Developer

Andrey Gershun & Mathias R. Wulff

Dgraph Labs, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Ultipa

Initial release

2014

2016

1995

2009

under the name LiveDB

2019

Current release

9.0.0, July 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

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

C and C++

Server operating systems

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

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

yes

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.

yes

with proprietary extensions

APIs and other access methods

JavaScript API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

RESTful HTTP API

Supported programming languages

JavaScript

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

yes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication via Raft

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Write ahead log

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

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.