DBMS > mSQL vs. OrigoDB vs. PostGIS vs. Sequoiadb vs. Transbase

System Properties Comparison mSQL vs. OrigoDB vs. PostGIS vs. Sequoiadb vs. Transbase

Editorial information provided by DB-Engines

Name

Description

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Spatial extension of PostgreSQL

NewSQL database with distributed OLTP and SQL

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Spatial DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

hughestech.com.au/products/msql

origodb.com

postgis.net

www.sequoiadb.com

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

Technical documentation

origodb.com/docs

postgis.net/documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

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

Developer

Hughes Technologies

Robert Friberg et al

Sequoiadb Ltd.

Transaction Software GmbH

Initial release

1994

2009

under the name LiveDB

2005

2013

1987

Current release

4.4, October 2021

3.4.2, February 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

GPL v2.0

Open Source

Server: AGPL; Client: Apache V2

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
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

oid, date, timestamp, binary, regex

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

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

proprietary protocol using JSON

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

.Net
C++
Java
PHP
Python

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

Server-side scripts

Stored procedures

yes

user defined functions

JavaScript

yes

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

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

based on PostgreSQL

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Document is locked during a transaction

yes

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

Role based authorization

yes

based on PostgreSQL

simple password-based access control

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Make Your MySQL Server More Secure With These 7 Steps - MUO
1 December 2022, MakeUseOf

Writing a Web Service in Perl
9 July 2003, PCQuest

provided by Google News

Share this page