DBMS > EJDB vs. GeoMesa vs. Microsoft Azure SQL Database vs. mSQL vs. OrigoDB

System Properties Comparison EJDB vs. GeoMesa vs. Microsoft Azure SQL Database vs. mSQL vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Database as a Service offering with high compatibility to Microsoft SQL Server

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Primary database model

Document store

Spatial DBMS

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

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

Website

github.com/Softmotions/ejdb

www.geomesa.org

azure.microsoft.com/en-us/products/azure-sql/database

hughestech.com.au/products/msql

origodb.com

Technical documentation

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

www.geomesa.org/documentation/stable/user/index.html

docs.microsoft.com/en-us/azure/azure-sql

origodb.com/docs

Developer

Softmotions

CCRi and others

Microsoft

Hughes Technologies

Robert Friberg et al

Initial release

2012

2014

2010

1994

2009

under the name LiveDB

Current release

5.0.0, May 2024

V12

4.4, October 2021

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

commercial

free licenses can be provided

Open Source

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

Server operating systems

server-less

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

yes

A subset of ANSI SQL is implemented

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

APIs and other access methods

in-process shared library

ADO.NET
JDBC
ODBC

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

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

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

Transact SQL

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes, with always 3 replicas available

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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.

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

PostgreSQL is the DBMS of the Year 2020
4 January 2021, Paul Andlinger, Matthias Gelbmann

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

The popularity of cloud-based DBMSs has increased tenfold in four years
7 February 2017, Matthias Gelbmann

show all

Recent citations in the news

Copilot in Azure SQL Database in Private Preview
27 March 2024, InfoQ.com

Microsoft unveils Copilot for Azure SQL Database
27 March 2024, InfoWorld

Azure SQL Database migration to OCI - resources estimation and migration approach
11 January 2024, blogs.oracle.com

Expand the limits of innovation with Azure data
21 March 2024, Microsoft

Why migrate Windows Server and SQL Server to Azure: ROI, innovation, and free offers
25 April 2024, Microsoft

provided by Google News

Higher Education PS rules out ghost students before PAC
29 November 2018, diggers.news

provided by Google News

Share this page