DBMS > GeoMesa vs. LokiJS vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. SWC-DB

System Properties Comparison GeoMesa vs. LokiJS vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

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

In-memory JavaScript DBMS

Microsofts flagship relational DBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

www.geomesa.org

github.com/techfort/LokiJS

www.microsoft.com/en-us/sql-server

www.sap.com/products/technology-platform/sql-anywhere.html

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

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

techfort.github.io/LokiJS

learn.microsoft.com/en-US/sql/sql-server

help.sap.com/docs/SAP_SQL_Anywhere

Developer

CCRi and others

Microsoft

SAP

formerly Sybase

Alex Kashirin

Initial release

2014

1989

1992

2020

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

17, July 2015

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

commercial

restricted free version is available

commercial

Open Source

GPL V3

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

Scala

JavaScript

C++

Server operating systems

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

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

via views

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
HTTP API
JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

JavaScript

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

C++

Server-side scripts

Stored procedures

View functions in JavaScript

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single collection possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

User concepts

Access control

yes

depending on the DBMS used for storage

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.