DBMS > GeoMesa vs. Linter vs. Memcached vs. SAP HANA

System Properties Comparison GeoMesa vs. Linter vs. Memcached vs. SAP HANA

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.

RDBMS for high security requirements

In-memory key-value store, originally intended for caching

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.geomesa.org

linter.ru

www.memcached.org

www.sap.com/products/hana.html

Technical documentation

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

github.com/memcached/memcached/wiki

help.sap.com/hana

Developer

CCRi and others

relex.ru

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

Initial release

2014

1990

2003

2010

Current release

5.0.0, May 2024

1.6.27, May 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

BSD license

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

C and C++

Server operating systems

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Proprietary protocol

JDBC
ODBC

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

yes

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

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.