DBMS > Altibase vs. EJDB vs. MySQL vs. Transbase

System Properties Comparison Altibase vs. EJDB vs. MySQL vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used open source RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.87
Rank	#200	Overall
	#93	Relational DBMS

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

altibase.com

github.com/Softmotions/ejdb

www.mysql.com

www.transaction.de/en/products/transbase.html

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

github.com/Softmotions/ejdb/blob/master/README.md

dev.mysql.com/doc

www.transaction.de/en/products/transbase/features.html

Developer

Altibase

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Transaction Software GmbH

Initial release

1999

2012

1995

1987

Current release

v7.3, 2023, August 2023

9.0.0, July 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free development 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

C++

C and C++

Server operating systems

AIX
HP-UX
Linux

server-less

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

yes

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL-92

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Java

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.