DBMS > GeoMesa vs. MarkLogic vs. OrigoDB vs. Snowflake

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Object oriented DBMS

Relational DBMS

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

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

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

docs.marklogic.com

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

CCRi and others

MarkLogic Corp.

Robert Friberg et al

Snowflake Computing Inc.

Initial release

2014

2001

2009

under the name LiveDB

2014

Current release

5.0.0, May 2024

11.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

commercial

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

Linux
OS X
Windows

Linux
Windows

hosted

Data scheme

yes

schema-free

Schema can be enforced

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

APIs and other access methods

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

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

user defined functions

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Source-replica replication

yes

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

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

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

Write ahead log

yes

In-memory capabilities

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.