DBMS > AlaSQL vs. GeoMesa vs. MarkLogic vs. OrigoDB

System Properties Comparison AlaSQL vs. GeoMesa vs. MarkLogic vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

Operational and transactional Enterprise NoSQL database

A fully ACID in-memory object graph database

Primary database model

Document store
Relational DBMS

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Object oriented DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

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

Website

Technical documentation

github.com/AlaSQL/alasql

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

docs.marklogic.com

origodb.com/docs

Developer

Andrey Gershun & Mathias R. Wulff

CCRi and others

MarkLogic Corp.

Robert Friberg et al

Initial release

2014

2001

2009

under the name LiveDB

Current release

5.0.0, May 2024

11.0, December 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

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

Scala

C++

Server operating systems

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

Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

Schema can be enforced

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

SQL92

APIs and other access methods

JavaScript API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

.NET Client API
HTTP API
LINQ

Supported programming languages

JavaScript

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

.Net

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

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

can act as a resource manager in an XA/JTA transaction

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

In-memory capabilities

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

yes

depending on storage layer

yes, with Range Indexes

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Role-based access control at the document and subdocument levels

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

Recent citations in the news

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

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

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

provided by Google News

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
22 April 2024, Medium

Database Platform to Simplify Complex Data | Progress Marklogic
7 February 2023, Progress Software

AI can make logistics data as valuable as intelligence or operational data for mission success
17 April 2024, Breaking Defense

ABN AMRO Moves Progress-Powered Credit Store App to Azure Cloud; Achieves 40% Faster Data Processing, Lower ...
12 March 2024, GlobeNewswire

Seven Quick Steps to Setting Up MarkLogic Server in Kubernetes
1 February 2024, Release.nl

provided by Google News

Share this page